$2.8K MRR│Looking for a technical partner

Hey Bernard,
have you considered hiring a fractional leader until you really have the need for someone permanent? This will help you avoid splitting company ownership just now...

Smart move. One thing I've noticed watching accounting workflows is that even in heavily automated firms, the communication layer still eats up a ton of time. Client emails, inquiry responses, report narratives. That stuff is still manual typing even when the bookkeeping engine is fully automated. I built DictaFlow to handle that part. Hold-to-talk dictation that types wherever your cursor is, about 3x faster than the keyboard. Might be worth adding to the platform roadmap at some point. dictaflow.io

Hi Bernard,

I came across your Indie Hackers post and the thing that caught my attention wasn't the AI angle or even the accounting market.

It was this line:

"The quality lives in the system, not in any individual."

That is exactly the kind of problem worth building.

My background is in full-stack development, automation systems, AI integrations, workflow orchestration, and building products from zero to production. Over the last few years I've increasingly focused on designing systems where humans supervise the process rather than perform every task manually.

What I find interesting about Northstone is that you're not trying to replace accountants. You're trying to codify accounting expertise into a repeatable system that can scale while maintaining quality. That's a much more defensible approach than most AI accounting startups.

A few thoughts I had while reading your post:

The bookkeeping engine and the future ERP platform are fundamentally the same product if the underlying accounting data model is designed correctly from day one.
Human review should become a measurable control layer rather than a manual workflow.
The most valuable asset may ultimately be the structured accounting knowledge and decision system that gets built along the way.

From your side, you already bring something many startups lack: paying customers, industry expertise, and a clear path to revenue.

I'd be interested in learning more about:

Your current client acquisition process.
How much of the bookkeeping workflow is already systematized.
What the next 12-24 months of product development look like.
Your expectations around technical ownership and equity structure.

If there's alignment, I'd be happy to discuss how I would approach building the engineering side of Northstone.

Best regards,

David

$2.8K MRR before looking for a technical cofounder is a way stronger spot than most posts here, you're negotiating from revenue not a deck. the thing i'd be upfront about early is equity, a profitable services biz with a product roadmap pulls really different people than a pre-revenue idea, and the good technical folks will wanna know if they're building the ERP dream or babysitting the bookkeeping engine that pays the bills. kind of two different cofounders tbh. anyway, hows the split looking given you're already cashflow positive, idk if you've even got there yet

Hi there, interested in this. Here's a MVP of cool B2B SaaS product I built recently => wholetrade

The "quality lives in the system, not the individual" framing is the most interesting thing in this post - that's the actual product, and it's a harder problem to solve than most AI accounting tools acknowledge.
One question worth thinking about for the co-founder search: the Denmark market is relatively small and the roadmap ends at an ERP platform, which is a very different engineering challenge from the bookkeeping engine. Are you looking for someone to build the current product well, or someone who wants to be there for the full 10-year arc? Those are different people.
Congrats on profitable early traction - that's a real foundation to recruit from.

hiqbyte.in

I've done work for OpenAI, Hulu+, and a ton of other companies, I've got over a decade of expereince as a software engineer with hands on experince with AI and building Agentic systems, would love to chat.

Hi Bernard,
One line got me: "the quality lives in the system, not in any individual." That's not a product feature, that's an architecture constraint , and the hardest one to actually build.
Here's what it actually means at the implementation level: your close engine can't just extract and route. Every decision the AI makes - VAT categorization, accrual logic, period matching - needs a traceable reasoning chain that a licensed bookkeeper can audit and stake their signature on. That's the difference between an AI that produces correct outputs and one that produces reviewable outputs. Most teams build the first and wonder why the human reviewer hates using it.
I've built this exact pattern in production and have worked with US and EU clients , AI outputs with step-level explainability feeding into a credentialed human approval layer. The architecture decisions there map directly to what you're describing.
On the ERP roadmap: the data model you design for bookkeeping will either enable or fight that pivot. That's a decision you make at month one.
Full-stack, AI-native, comfortable owning a codebase end to end. Have shipped production systems solo. Would love to explore it more with you !

Hi Bernard,

This looks like a solid opportunity. I'm a mobile/full-stack developer with strong experience shipping production apps most recently SleepViz , an iOS app I built and launched solo.

I'm comfortable owning a codebase end-to-end and building AI-integrated systems. You can see my work on GitHub: YounesseElkars

I don't have accounting knowledge, but from what you describe, I don't need to you own that half. I'd focus on turning your logic into reliable, scalable product.

Happy to jump on a call if you think there's a fit.

Youness

Hi Bernard, I am interested in learning more. Where can I contact you?

Hi Bernard,

I’m very interested in the technical co-founder opportunity for Northstone. Your AI-native accounting platform and profitable model are impressive, and I have experience building full-stack AI-powered systems, automation pipelines, and end-to-end product development, which aligns well with your roadmap.

I’d love to learn more about the role and discuss how I could contribute to building the product side. Could you clarify the structure of the paid component versus equity? I want to ensure there’s a sustainable balance as we grow the platform.

https://topstar-ai.github.io

I will wait for your message.
Best regards.

Interesting approach. Building the quality into the system instead of relying on individual operators is exactly where I think AI-enabled service businesses have an advantage.

We've been helping startups and growing companies build AI-powered SaaS platforms, workflow automation, ERP solutions, and custom business applications. Your roadmap from bookkeeping to a full ERP platform sounds like a strong long-term opportunity.

If you're open to exploring a technical development partner alongside your co-founder search, we'd be happy to connect and share how we've helped similar businesses scale their products.

https://www.elsner.com/contact-us/

Hey Bernard,

I've been building AI-heavy B2B SaaS products for 7+ years — legaltech, fintech, document-heavy systems. The last few years specifically working with early-stage founders as their first technical person across India, US, and Dubai — taking full ownership, making product and architecture decisions, shipping from zero.

The kind of work you're describing — AI running intake, task generation, QA, then a human signs off — I've built exactly this pattern. Document processing pipelines, verification systems, accuracy going from broken to production-grade. That's the core of what your close engine needs.

I work retainer + small equity, which sounds like what you have in mind. Outcomes-based, phase by phase, you always know what's getting built.

I don't know Danish accounting — don't need to, that's your half. My job is turning your logic into something that scales.

LinkedIn: linkedin.com/in/sood2105
WhatsApp: +91-8628825125

Happy to jump on a call.

Interesting post.

The thing I'd be careful with is that finding a technical partner and convincing the right technical partner are not necessarily the same problem.

You clearly have revenue, industry knowledge, and a roadmap. The harder question may be which part of the opportunity the strongest candidates actually anchor on when deciding whether to join.

I would not make that call casually in a thread because it changes how the entire opportunity is presented.

Curious what kind of responses you're getting so far.