You make the introduction.
For anyone, company or individual, who knows a business that needs software built. You make the introduction and step back. We run the relationship from there, and you get a referral commission if the deal closes.
Partners
Partnerships that change what we can build.
A partner badge is only worth showing if it gives you something. These give us access, escalation paths, and in one case an independent appraisal of how we deliver.
Partnerships and certifications
What each one gets you
AWS Partner Network
Architecture review and a support path when infrastructure is the constraint.
Stripe Verified Partner
Verified integration practice for payments, including PCI scope reduction.
Shopify Plus Partner
Plus-tier access for commerce builds, replatforms and StorefrontOS.
CMMI-DEV/3
An independent appraisal of our development process, not a self-assessment.
ISTQB and CAT
Certified testers, which matters when quality is a contractual gate.
Scrum Alliance
Certified ScrumMasters, for the clients who still run Scrum internally.
Recognition we did not pay for
Our work has taken Indigo Design Awards across Luna, Nab, Fashioned Health, FlightLogger and our own website, including Gold for UX, Interface and Navigation. Clutch has named us among the top developers in Latin America, and Inc. named Koombea a Power Partner.
Partner with us on delivery
The partnerships above are ones we hold. This is the other direction: a program for people who want to send work to us, or who need delivery capacity behind work they have already won.
There are two models and they are genuinely different, so it is worth knowing which one you are asking about before you fill in the form.
Two Models, Not a Spectrum
You keep the client, we build.
For agencies and software companies with more demand than capacity, or with work outside what their team does. You own the client relationship and the commercial terms. We deliver against a committed scope behind you, at whatever level of visibility you want.
Either way the commercial basis is the same as any other engagement. Scope is defined upfront and priced in story points, so what you quote your client and what you owe us are both known before work starts.
How a partnership starts
The first conversation is about the specific project, not about the program. We need to know what has to be built, what it has to integrate with, and what has already been promised to whom.
From there it is the same scoping process as any engagement. Scope goes into a Work Breakdown Structure, gets priced in story points, and both sides agree it before anything is committed. That matters more in a partnership than anywhere else, because you may have already quoted your client and a price that moves later is your problem, not ours.
- One call about the project, not a program pitch
- A Work Breakdown Structure and a story point price before commitment
- Delivery in two-week cycles, with whatever reporting you need to pass on
- An honest answer when the work is a poor fit for this model
Interested in partnering with us?
Tell us which model fits and what the work looks like. If you are not sure which one, describe the client situation and we will tell you.
2 years ago when I started working with Koombea, I would have just used the term client, but now I think of them as a real business partner.
Bring us the backlog.
In 30 minutes, we will show you what a Pod would ship first and how we would price it.