The Build Partner Program
Why We're Giving Away Our Best Work
We waived implementation fees for our first 10 clients. Here's why that's strategy, not charity.

Wilfred Greyling
Systems & Infrastructure
TL;DR
We waived implementation fees for our first 10 clients. Not charity, strategy. Building alongside real businesses teaches us what no whiteboard session ever could.
The Decision
We made a choice that looks strange from the outside: take the most valuable thing we offer, full operational stack implementation that normally costs R 40k – R 80k, and give it to our first 10 clients for free. Not a discount. Not a trial. Free. The assessment, the tool selection, the deployment, the automation workflows connecting everything together. The entire thing, delivered at zero cost.
People hear this and assume it's a marketing gimmick, or that the product isn't ready, or that we're desperate for customers. None of those are true. The product works. We could charge for it today and people would pay. We chose not to, for 10 specific businesses, because we realized that the value of building alongside real companies far outweighs the revenue we'd collect from those first engagements.
Here's the honest thinking: we can build what we think businesses need, or we can build what businesses actually need. Those are different things. Every software company that's failed has a version of the same story. They built something clever in isolation, launched it, and discovered that the real world doesn't match the whiteboard. We decided to skip that chapter entirely.
What ReadyRun Loop Actually Is
Let's be precise about what this is. Loop is not a beta test. You're not clicking through half-built screens and filing bug reports. It's not a free trial with a paywall waiting at month three. And it's not charity. It's a build partner program. 10 businesses get their full open-source operational stack deployed and configured, the same implementation we'd deliver to a paying client. In exchange, they build the product alongside us.
Their real workflows, real pain points, and real feedback shape what ReadyRun becomes. When a build partner says "this doesn't work for how we actually do invoicing," that's not a complaint. It's product direction. When they discover that the automation between their CRM and project management breaks on a specific edge case, that's not a bug report. It's a gift.
What Build Partners Receive
- Full operational assessment across 41 business domains
- Open-source tools selected, deployed, and configured for your business
- Automation workflows connecting your tools from day one
- Clear gap analysis showing where you're covered and where you're not
- Direct access to the build team for 12 months
What Build Partners Get
The assessment alone is substantial. It maps your business against over 1,100+ capabilities across 41 operational domains, everything from how you handle client onboarding to whether you have a disaster recovery plan. Most businesses have never seen their operations laid out this comprehensively. The result is a coverage score that shows, in concrete terms, where you're strong and where the gaps are hiding.
The deployment covers the tools that matter most: CRM, project management, team communication, document management, knowledge bases, workflow automation. All open source, all self-hosted, all connected. Not cobbled together with manual exports and copy-paste between tabs.
These tools are connected with automation workflows that move data between systems the moment something happens. A deal closes in your CRM and an onboarding project spins up automatically. A support ticket escalates and the right people know immediately. Your tools work as a system, not a collection of islands.
And then there's the access. Build partners don't go through a support queue. They talk directly to the engineers and architects building the product. When something doesn't work, it gets fixed, not logged and triaged and scheduled for a future sprint.
When a build partner has an idea that would make the product better for their business, it gets heard by the people who can build it. That kind of access is genuinely rare, and it's only possible because we're working with 10 businesses, not 10,000.
What We Get
Transparency matters here, so let's be direct about what's in it for us. We get real workflows to test against, not hypothetical scenarios dreamed up in a planning session, but the actual messy, complicated, exception-riddled processes that real businesses run every day.
A dental practice's patient intake flow doesn't look anything like what you'd sketch on a whiteboard. A logistics company's vendor management has edge cases that no amount of internal brainstorming would surface. That's the kind of reality we need.
We get real feedback from people who depend on the software every day. There's a massive difference between someone clicking through a demo and saying "looks good" and someone who just lost 30 minutes because an automation didn't fire correctly. The second person will tell you exactly what's wrong, exactly how it should work, and exactly how urgent it is.
That feedback is brutal, specific, and invaluable. It's the kind of feedback you can't buy. You can only earn it by giving people something they rely on.
And eventually, we get real case studies. Not manufactured testimonials or cherry-picked metrics. Real stories from real businesses about what their operations looked like before, what changed, and what the impact was. That kind of proof, told by the businesses who lived it, is worth more than any marketing campaign we could run.
Why Not Just Build It Ourselves
The honest calculation is simple: software built in isolation works in theory. Software built with 10 real businesses works in practice. Every assumption we make in a meeting room, a build partner will challenge with reality. Every workflow we design based on best practices, a build partner will break with the way they actually work. Every edge case we'd discover six months after launch, they'll surface in week two. The difference between "we think this works" and "we know this works because 10 businesses depend on it" is the difference between a product and a prototype.
The investment in build partners isn't generosity. It's the fastest path to a product that works. We could spend 18 months building in isolation, launch, and then spend another 12 months fixing everything that doesn't match reality.
Or we could spend those same 18 months building alongside the businesses who'll use it, and launch with something that's already been tested, challenged, and refined by the people it was built for. The math isn't even close. The build partner approach is faster, cheaper, and produces a dramatically better product. The only cost is the implementation revenue we forgo, and we think that's a bargain.
Who This Is For
Not every business. And not every business that applies will be selected. We're looking for specific characteristics, businesses where the partnership will be genuinely valuable for both sides. The wrong fit wastes everyone's time. The right fit changes the trajectory of both the business and the product.
Here's what we're looking for:
Build Partner Criteria
- 10-50 employees : Big enough to have real operational complexity, small enough to be agile
- Things aren't connected : You know your tools don't talk to each other, and you feel the cost of that every day
- Willing to give honest feedback : This is a partnership, not a handout. We need you to tell us what's broken
- Ready to grow : You're building for what's next, not just maintaining what is
Industry doesn't matter. We want diversity across the 10 partners. A professional services firm, a healthcare practice, a retail operation, an e-commerce business. The more varied the mix, the more robust the product becomes. What matters is that you're at the stage where operational infrastructure is becoming a real constraint on growth, and you're willing to invest the time to build something better alongside us.
How Many Spots Are Left
10 spots total. We're selecting partners now. If this sounds like your business, if you're feeling the weight of disconnected tools and manual processes and you're ready to fix it properly, join the waitlist below and check the Loop interest box. We'll reach out to discuss whether it's the right fit for both sides. You can also visit the full Loop page for more details on the program structure and what to expect.
Interested in Being a Build Partner?
Join the waitlist and check the Loop box. We'll be in touch to discuss whether the partnership is the right fit.