What Didn't Work: Building More Doesn't Fix a Distribution Problem
JAMARQ got much better at building things this year. It did not get much better at selling them. That's the honest summary, and it's the most useful thing the year produced. This is the fourth of five notes this week.
October 29, 2026
The short version
I'm working with essentially the same clients I started with. My technical range grew a lot over the year. My client list didn't.
That isn't a complaint, and it isn't a confession. It's information, and it turned out to be the clearest information the whole year produced.
Where the work came from
Most of JAMARQ's work came through family businesses and people I already knew. That's a good way to start. You learn on real projects with people who are patient with you, and several of those businesses already relied on me for their IT before there was ever a website.
What it didn't turn into was the referral pipeline I'd hoped for. Good work for a small circle of businesses mostly stays inside that circle. Earlier attempts at approaching local businesses directly didn't go much better.
What I did instead
When there wasn't new client work, I did what I'm good at: I built.
I made the existing sites faster and sturdier. I moved them to a better platform. I learned new tools and wrote software. Most of that work was worth doing, and the client sites are better for it.
But a lot of time also went into polishing things nobody had been shown yet. It's easy to tell yourself something isn't ready. There's always one more thing to fix before anyone sees it, and every one of those things feels responsible.
The clearest example is a little embarrassing. I built an app specifically for drafting and scheduling social media posts. JAMARQ's own social accounts sat untouched the entire time.
What I stopped on purpose
Not everything that ended was a failure. For a while, part of the work ran under a separate brand called Tenra. One person maintaining two identities stopped making sense, so I retired it rather than keep it alive just because I'd already put time into it.
That's a skill I'd like to use more often: noticing when something is being kept going out of momentum rather than because it still earns its place.
What it taught
The building wasn't wasted. The tools work, the client sites are better, and I can do things now that I couldn't a year ago. Taking a live site from shared hosting to a modern platform without anyone noticing is not something I could have done well at the start of the year.
But building more cannot solve a distribution problem. Nobody hires you for work they don't know exists, and nobody refers you for work they've never seen. Every hour spent refining something in private is an hour it isn't doing anything for anyone.
So, this week
The next phase isn't another tool. It's showing the work, as it happens, in plain language. This series is the first step: what got built, what didn't work, and tomorrow, what JAMARQ actually is now.
