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 New Zealand's leading open banking infrastructure platform and has a small team. The other automates accounts payable with AI and is just me.
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 are already obsolete. 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 New Zealand's leading open banking infrastructure platform, the rails that let apps connect to bank accounts. The timing matters. New Zealand's regulated open banking regime came into effect on 1 December 2025, and Akahu sits right in the middle of that shift. 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, assigns tracking categories, gathers the relevant 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. The future of software companies isn't 500 people in an office. It's a small number of founders with systems doing work that used to require headcount.
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.
Use this post as the map. The other essays go deeper on individual parts of the argument.
How this publication works
This publication is itself part of the experiment. The entire pipeline, from idea capture through to publishing and audience feedback, runs on AI infrastructure I built. My job is to think and review. The rest is execution.
When I have an idea or read something interesting, I email it to a notes address. AI cleans it up, files it, and tags it. Every night, a synthesis system reads all my notes, looks for patterns, and clusters related ideas together. When a cluster has enough weight to become a post, it drafts one. I review it, rewrite the parts that don't sound like me, and publish it.
After publishing, it keeps working. Reader replies and engagement signals feed back in. The system tracks which ideas resonated and which didn't, and that shapes what gets surfaced next.
None of this is finished. The whole thing is an experiment in learning. The system gets better as it runs, I get better as I write, and the publication gets more useful as the loops tighten. But the principle is bigger than a newsletter. If the judgment is still human, one person should be able to operate with something closer to a chief of staff and a full team at their disposal, across work and life, without the actual headcount. The thinking is mine. The standards are mine. The machinery is not. This newsletter is just 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. That's already happened in the first week, which tells me this is worth taking seriously.
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.
If you're starting to think seriously about what open banking means for your business, or want to schedule a demo of AI-enabled accounts payable automation for large organisations on Xero, get in touch. Both of those are very real parts of my day job.
I'm Ben Lynch. I think about founders, AI, and what happens next from New Zealand. Say hello at ben@thinkdorepeat.ai.
If you came here from the end of another post, now you have the frame. Subscribe if you want the essays as they come out.