Home/Company/Partners
Company

We work with all of them. We are paid by none of them.

Most firms calling themselves a partner earn something when you buy. We do not — no commission, no referral fee, no margin, no tier. That is the only reason our recommendation is worth anything.

Headquartered in the United States · working worldwide

Platforms we build on
and what we are paid by each of them
$0in commission
PlatformWhat we do with itCommission
Salesforceimplement, extend, audit, replacenone
HubSpotoptimise, integrate, migrate offnone
Odooimplement, upgrade, refactor forksnone
Zohoconsolidate, document, extendnone
GoHighLeveltake ownership, operate, migratenone
Anthropic, Twilio, Stripeand the rest of the stackbuild against their APIsnone
0 referral fees, 0 partner margins, 0 tierswhich is why we can tell you to stay
0
Zero commission, on everything
including the ones we recommend most
In practice

What being paid by nobody actually changes.

Neutrality is easy to write on a page and only visible in decisions. These are the ones where the arrangement shows, including the two that cost us work.

01You are on a platform we would not have chosenYou get both numbers — what it costs to fix what you have, and what it costs to leave — before either of us has an opinion about which.
02The answer is a setting you already pay forThen that is the recommendation, and it is the one that bills us least. It is also the most common one we make.
03A higher licence tier would raise your spendWe have no share of your invoice and no visibility of it. The seat count and tier we suggest are the ones the process needs.
04A vendor offers a referral fee mid-engagementDeclined. Disclosing a fee does not undo it — you would still have to work out what it changed, and that is work we are asking you to do.
05You ask which platform we are certified inNone of them. There is no exam we have passed that should carry weight in a decision this expensive.
06The honest answer is that you do not need usYou are told in the first conversation, which is why the first conversation is a diagnosis rather than a pitch.
The stack

Everything we have shipped against.

Platforms we implement, services we build on, and infrastructure we run. None of these marks means a partnership — it means we have shipped production code against their API. Hover to pause.

30+PLATFORMS

CRM and business platforms

Salesforce, HubSpot, Odoo, Zoho, GoHighLevel, NetSuite. Implemented, extended, audited, and occasionally migrated away from — which is the same list read in the other direction.

Data, reporting and attribution

Postgres, Segment, Plaid, Retool, and the Google Ads, Meta and LinkedIn APIs. Server-side events and warehouse loads, because the browser stopped being a reliable place to measure from.

Communications, money and paper

Twilio, Stripe, QuickBooks, DocuSign, Ramp, Cal.com. The half of a workflow where a duplicate write costs somebody real money rather than a wrong number on a chart.

Build, run and page

AWS, Vercel, Docker, Terraform, GitHub, n8n, and the Anthropic and OpenAI APIs. Where what we build is deployed, watched, and where the alert lands at 2am.

The bar for appearing above is narrow on purpose: production code, running for a client, that we were the ones called about when it broke. Trials, prototypes, sandbox builds and courses do not count, which is why the list is shorter than a partner page usually is.

Why it matters

A recommendation you are paying for is not a recommendation.

Certification tells you somebody passed an exam. It tells you nothing about whether they will say the honest thing.

01

A partner earning margin on a licence has a reason to recommend that licence, whatever your process needs.

02

Tier status is earned by selling volume, not by delivering well.

03

The firms with the highest certifications are frequently the ones least able to tell you to buy something else.

04

We are not in any partner programme, which costs us leads and buys us the ability to be straight with you.

05

When we say stay on HubSpot, there is nothing in it for us either way.

06

When we say replace Salesforce, the same is true — and it happens far less often than you would expect.

The standard

How a recommendation actually gets made.

Five steps, in this order, every time. The order is the point: staying is priced before leaving is, so the expensive option never gets to be the only one with a number attached to it.

01

Read what you already have

the inventory

Every automation, field, integration and report, and who depends on each. Almost no estate can produce this list, and producing it is where the finding usually is — before any platform has been discussed.

02

Separate the process from the software

the constraint

Whether the thing that does not work is the platform's object model or a decision somebody made inside it years ago. Only the first is a reason to move, and it is the rarer of the two.

03

Price staying

a real number

What it costs to fix what you have, including the configuration everyone has been avoiding. This number is produced first, deliberately, because it is the one a firm with a licence margin has no reason to produce at all.

04

Price leaving, with the same rigour

the whole cost

Migration, rebuild, number re-porting, the reporting history that does not come with you, and the months where both systems run. Written down rather than estimated in a meeting.

05

Say which, and why, in writing

the recommendation

With the losing option's number printed next to it. You should be able to see what the recommendation cost you rather than take on trust that it was weighed.

Questions

What people ask about the arrangement.

Are you a Salesforce partner?

No — and not a HubSpot, Odoo, Zoho or GoHighLevel partner either. We are not enrolled in any vendor programme, hold no tier, and sit no certification exams.

Then how do you know these platforms?

By shipping production code against them for clients who depend on it, and by being the ones called when it broke. That is a slower way to learn a platform than a certification track and a more honest signal of whether we can operate one.

Do you earn anything at all from software you recommend?

No commission, referral fee, partner margin, reseller discount or revenue share, on anything, ever. Where a vendor offers one, we decline it rather than disclose it.

Do you resell licences?

No. You buy directly from the vendor, in your own name, on your own card. We never sit between a business and a licence it depends on — that is the same failure mode as an agency holding your account.

Would you tell us to stay on a platform you did not build?

Routinely, and it is the most common recommendation we make. A platform being wrong for somebody else's process says nothing useful about yours.

What does “shipped against” mean on the stack list?

Production code, running for a client, that we were responsible for when it failed. A trial, a prototype or a sandbox build does not put a platform on that list.

What if we would rather have a certified partner?

That is a reasonable thing to want, and we will say so. Certification is real evidence that somebody knows a product. It is just not evidence that they will tell you not to buy it.

Does neutrality cost us anything?

Yes, and it is worth knowing what. You lose the vendor introductions, the escalation paths and the programme discounts a tiered partner can sometimes pass on. You gain a recommendation nobody paid for. We think that is the better trade, and you should make it deliberately rather than by accident.

Who owns what you build on these platforms?

You do, from the first commit — repository, configuration and credentials, in your organisation rather than transferred at the end. The full ownership terms sit with how we work.

Ask us what we are paid by.

Then ask the next firm, and ask in writing. It is the cheapest piece of due diligence available to you, and the answers vary more than anyone expects.

Partner programmes
None, on any platform
Commission
Zero, on everything
Licences
Bought by you, in your name
Code
Yours from commit one