The thesis

This is the first Solo Letter. There will be more. Quarterly, if I can hold the cadence; whenever the material is ready, if I can't. They are not a changelog. They are not a feature announcement. They are the long-form version of what is actually happening with Kinako — the numbers, the trades I am making, the things I am wrong about — written for the other solos who are trying to do something similar.

I want to start with the thesis. Everything else this publication will be about flows out of it.

The thirty-year delta

For thirty years, the difference between a solo who succeeded and one who didn't was experience. Not intelligence. Not appetite. Not access to capital. Experience — the operators who had already drafted a hundred proposals, sent a thousand invoices, lost the deals that taught them what to do differently. Scar tissue.

You couldn't fake it. You couldn't buy it. You had to earn it the slow way — usually somewhere between two and ten years of doing the work badly before doing it well. The new freelancer's first proposal looked like a new freelancer's first proposal. Their first follow-up email read like a first follow-up email. Their first invoice was sent late, in the wrong format, with a payment term they had not thought through. None of this was a moral failing. It was the cost of starting.

Most of the people who succeeded paid that cost. Most of the people who quit paid the same cost and ran out of runway first.

That delta — the gap between someone with the scar tissue and someone without it — is the entire reason a thirty-five-year-old consultant out-earned a brilliant twenty-three-year-old by an order of magnitude. The thirty-five-year-old wasn't smarter. They had simply done the thing more times.

What AI actually changed

I am not interested in the maximalist version of the AI argument. The version where the freelance business "runs itself" is dishonest. It does not run itself. It cannot run itself. A solo who hands their operation to autopilot will discover, very quickly, that the autopilot has no idea who their client is, what was promised in the last meeting, or why the proposal needs to be priced thirty percent below market this quarter.

What AI changed is more specific. It collapsed one particular cost: the cost of producing the first draft of work that an experienced operator would produce.

The proposal that used to take three hours because the new freelancer had no template, no language, no rhythm — that draft now takes ninety seconds. Not because the AI is creative. Because the AI has read a million proposals and it knows what one is supposed to look like. The follow-up email that the new freelancer would have stared at for forty minutes — that draft now exists in the second you ask for it. Not because the AI knows your client. Because the AI knows what an experienced operator would write to a client of that type in that situation.

The reading of the email, the judgment about whether the draft is correct, the decision to hit send — those still belong to the operator. The blank page does not.

This is the part of the AI argument I will keep making. It is the part I think is honest. Experience, on day one, is not "AI replaces the operator." It is "the operator no longer has to start from zero each time, because the scar tissue is now downloadable as a draft."

What Kinako is

Kinako is the software shape that delta takes when it is delivered to solos.

Concretely: it is the business operating system — CRM, proposals, contracts, invoicing through Stripe, scheduling, time tracking, expense tracking, intake forms, welcome documents, a client portal — that every solo runs anyway, with an AI layer that produces the first draft of every piece of operator work you would do inside it.

The Daily Briefing tells you, every morning, what an experienced operator would have noticed about the state of your business. The proposal you have not heard back on. The invoice that is six days overdue. The meeting you have not prepared for. The client you have not spoken to in sixty days who is statistically about to churn.

The AI Draft writes — anywhere in the product where there is a blank field — the first version that an experienced operator would have written. You read it. You edit it. You decide what to send. The software never sends, signs, or charges anything without you.

The third thing — and this is the part I find most interesting — is that every public-facing surface in Kinako (every proposal, every invoice, every contract, every client portal, every booking page) is built so that your clients see operator-grade output even on your first day. The audit log of "first proposal sent" looks the same on day one as it looks on day one thousand. There is no version-zero embarrassment.

That is the product. It is one tab. It is nineteen dollars a month. It is built by one person — me — at the level of craft I would build it at if a company were paying me a salary to do it.

A note on craft

Kinako has Row-Level Security on every table. Every Stripe webhook is idempotent. Every public share-token route is rate-limited and audit-logged. The UI is hand-built — no Material UI, no shadcn fallback, no component library. There are forty-plus tables in Postgres. There is exactly one owner of the code, which is me.

I mention this not to flex. I mention it because the temptation, when you are a solo founder building under time pressure, is to skip the parts that do not show on the surface. To leave RLS off because nobody is going to attack a side project. To call auth.getUser() without a token check because most users will not poke at it. To ship the Stripe webhook without idempotency because duplicates are rare.

I made a decision early on to not skip those parts. The trade is that I am slower than founders who do skip them. The trade is also that Kinako does not have the kind of fragility that shows up six months after launch, when the database that was designed for ten users hits a thousand and the founder discovers that they have to rebuild it.

You should not have to choose between a tool that looks polished on the surface and a tool that is built well underneath. Kinako is the bet that you do not have to.

Where this publication is going

These letters will be honest. That is the most useful thing I can promise about them.

I will share real numbers: paying customers, MRR, conversion rates, what is working, what is not. I will share the trades I am making and the reasons. When I am wrong about something — and I will be wrong about things — I will write the next letter explaining what I missed and what I changed.

I do not have a content strategy in the sense most people use that phrase. I am not optimizing the publication for keywords. I am writing what I would want to read if I were in your position: the long-form version of what is actually going on inside another solo's company.

The expected cadence is quarterly. The expected length is what these are — somewhere between fifteen hundred and three thousand words, depending on how much there is to say. I will write them in long-hand voice. I will not pad them. If a Letter could have been a paragraph, I will write a paragraph.

Where we are right now

Kinako is live at kinako.app. The product covers everything I described above. The price is nineteen dollars a month, with a free plan that gets you three clients, three projects, and three invoices — enough to actually try it on a real client without the wallet question getting in the way.

I am writing this letter from a desk in Melbourne, between a 9-to-5 job in HR at National Australia Bank and the hours that I spend on Kinako every night and weekend. The day job pays the bills. Kinako does not, yet. The moment it does, I am out, and the next Letter will say so.

The product is built. The story is half-told. The customers are early. That is the honest read of where this thing is on May twenty-third, twenty-twenty-six.

If you are a solo trying to figure out whether to start, the line I want you to take from this Letter is the simplest one: you no longer have to start at zero. The scar tissue is downloadable. The day-one version of your business can look like the year-ten version, if you build it on top of software that does the operator work for you.

That is what I am building. That is why. The next Letter will be about what happens when it meets the market.

— Jhayden