We build inside what you already pay for.
We hold no reseller agreement and no partner badge with any vendor on this page. You buy your own licences, direct, at the price the vendor publishes. We build on the product and we are paid by you — which is the only arrangement in which we can tell you that the cheaper plan is enough, or that the thing you are about to buy will not fix it.
Certified developers, working together on one problem at a time. Every price we charge sits on one page, and none of them changes with the platform.
The base, the views, the automations and the interfaces. Usually it starts as a spreadsheet that outgrew itself, and ends as something a team can run without asking anyone how it works.
For a team already in Airtable, or one about to leave a spreadsheet for it.
What to watch for. Airtable runs one process in memory per base. The per-base limits are how it is built, not a setting waiting to be raised, so a base that has hit them needs splitting rather than waiting.
Records that disagree with each other, and the jobs that should run off them — lead routing, deal-stage triggers, enrichment, alerts, and getting data in or out without losing half of it.
For a team whose CRM is the system of record and no longer trusted as one.
What to watch for. HubSpot is eventually consistent and gives no ordering guarantee — a write can take seconds or minutes to be readable. Anything built on it has to be written to expect that, not hope.
Power Automate, Microsoft 365, SharePoint, Power BI, Azure and Fabric. The job is the same job we do anywhere else — a run that starts itself, two systems joined, paperwork read — it just happens to run on Microsoft.
For a team already paying for Microsoft 365 and not using most of it.
What to watch for. The free Power Automate licence covers standard connectors only — Microsoft’s own wording. The moment a flow needs a premium or custom connector it needs a paid Power Automate licence on top of Microsoft 365, which is the cost most often missed when the work is scoped.
Liquid work on the theme, product configurators and variant pickers, Shopify Functions, Plus checkout and B2B, and orders routed onward to Klaviyo, Printful or a warehouse and back again.
For a store whose theme or checkout has to do something the theme cannot.
What to watch for. Shopify’s own wording: only stores on a Shopify Plus plan can use custom apps that contain Shopify Function APIs. Any plan can get the same behaviour from a public app in the App Store, so the plan does not decide what is possible — it decides how it has to be built.
What a partner badge actually buys, and who pays for it.
-
A badge measures sales.
The tiers on these programmes are counted in licences sold and revenue booked, not in systems that work. A firm can hold the highest badge a vendor issues without ever having built the thing you are about to ask for.
-
The badge is bought, and somebody pays for it.
These programmes charge to join, and the tiers above the entry one are reached by booking revenue for the vendor. That cost does not disappear. It comes back through the licences a client is advised to buy.
-
What we do instead is name what we touch.
Each page below this one lists the modules, the editions and the API limits we work against, including the ones that make a job harder. That is checkable by anyone in an afternoon, which a badge is not.
-
And we will say when the answer is a different platform.
Nothing on this page pays us to keep you where you are. If the base has hit a limit that will not lift, or the feature you need sits on a tier above the one you are on, that is the answer and we would rather give it early.
True whichever platform you are on.
-
You buy the licences, and the invoice stays between you and the vendor.
We hold no reseller agreement with any vendor on this page, so nothing we recommend earns us a commission, a margin or a tier. It also means we can tell you the plan you are on is enough, which a reseller cannot afford to say.
-
The same job costs the same on any platform.
A run that starts itself costs the same whether it runs on Power Automate, on n8n or inside HubSpot. The platform changes how it is built, not what it is worth. Every figure sits on one page.
-
You own it, including the parts that are ours.
The code, the credentials and a written runbook. Yours from the first delivery, and yours outright the day the last invoice is paid. Hand it to your own developer whenever you like.
-
We publish the limit on each platform.
Every row above carries a limit, and none of them is small print. They are the reasons a build goes wrong in month six, and they are easier to read now than to discover then.
Seven systems running at named companies, and six of them you can open.
Every one was built for a named company and is running there now. Six have a copy on this site on invented records, so anyone can try one without asking us. The most detailed account of how we work inside a platform is on the HubSpot page, which lists the objects, the editions and the six things only building against the API teaches, and the Microsoft page does the same across seven products with the published limit on each. On the Shopify page the product is ours: an order-support app anyone can open on the App Store. The seventh, the Airtable work for a construction firm, opens that firm’s own system rather than a copy of it.
Tell us what you already pay for.
The platform, the plan you are on and the job that is not getting done. We will tell you whether it is a build, a fix, or a plan you already pay for and have not switched on. We reply within one business day.