Start Here
If you're new, this is the quickest way to understand what I'm building and why I write.
If you've landed here from one of my essays, this is the frame.
I'm the founder of two fintech companies from a small town north of Auckland. One, Akahu, is an open banking infrastructure platform with a small team. The other is an AI-native accounts payable company that's just me and the system.
That's not a brag. It's the thesis.
The economics of building software companies have changed so much in the last few years that a lot of the old assumptions already look shaky. How many people you need. How much capital you raise. What work actually needs a human. I'm testing that in the real world, with real customers and real stakes.
Think Do Repeat is where I write about what I'm learning.
The name is the method
Think. Read widely. Build mental models. Question the default assumption. Most people skip this step because doing feels more productive. It isn't. Bad thinking leads to busy work. Good thinking leads to leverage.
Do. Build something. Ship it. Put it in front of customers. Test the thinking against reality. I've been building software companies for over a decade. The doing is where the learning actually happens.
Repeat. Write it down. Not to teach anyone, but to force clarity. If I can't explain what I learned, I probably didn't learn it. Writing is thinking made visible.
That's the loop. Think, do, repeat. Everything I write here comes from somewhere in that cycle.
Who I am
I'm Ben Lynch, based in Matakana, New Zealand. Former Xero engineer, now a solo founder.
Akahu is my first company. It's open banking infrastructure, the rails that let apps connect to bank accounts. A small team runs it day to day.
Most of my current product development work is in an AI-native accounts payable platform. Invoices come in, the system extracts the data, codes them, gathers the organisational context, and posts them into Xero. It's like having your own internal AP team, without the headcount. It's just me and the system.
I didn't set out to build companies this way. I've always had more ideas than execution capacity. AI changed that equation. I kept not hiring, kept finding that AI could handle the next thing I thought I'd need someone for, and eventually realised this wasn't just my situation. It was the pattern. For people with more ideas than hands, AI is the leverage that changes the game.
I have no social media presence. I don't go to conferences or networking events. I'd rather put the thinking into something worth reading than scatter it across platforms optimised for reaction. This publication is my only public outlet, and that's deliberate.
What to expect
I write about what I'm actually building and what it seems to imply.
That usually means AI as leverage, solo founding, building from New Zealand, and the gap between how companies say they work and how they actually work. Sometimes that becomes a post about economics or hiring. Sometimes it's an argument with a whole category of startup advice. Sometimes it's just a note from the middle of using these tools every day and seeing what holds up.
This isn't a fintech newsletter, and it's not a startup advice column. I'm not trying to build a personal brand or sell a course. It's one person thinking out loud, grounded in work with real consequences. Some of it will be wrong. I'll say so when I figure that out.
Think of the publication as one connected argument, not a collection of posts. The essays go deeper on individual parts of the same thesis: AI changes the economics of building, small teams can do far more than they used to, and a lot of accepted wisdom about software companies is about to age badly.
How this publication works
This publication is itself part of the experiment. The pipeline behind it runs on AI infrastructure I built. My job is to think, judge, and review. The rest is execution.
Ideas and reading get routed into that system. It organises them, finds patterns, drafts when there's enough substance, and feeds audience signals back into the next round. I still do the thinking. I still decide what's true, what matters, and what's worth publishing.
That's the broader point. If judgment stays human, one person should be able to operate with something closer to a chief of staff and a full team at their disposal, without the actual headcount. This publication is one visible proof point.
Why write at all
Writing forces me to think more clearly than I otherwise would. An idea that seems solid in my head often falls apart when I try to put it into sentences. That alone makes it worth doing.
But writing is also distribution. A good post gets forwarded to someone who needs to hear it. That opens doors no cold email ever could.
If something here makes you think, forward it to someone who'd find it useful. If you disagree with something, reply to any post and tell me why. I'm thinking out loud and seeing who turns up.
I'm Ben Lynch. I write about founders, AI, and what happens next from New Zealand. Say hello at ben@thinkdorepeat.ai.
If this gives you the frame, the rest of the publication fills in the argument.
If you know someone who'd care about where software and company-building are heading, send them here.