Package

API and platform strategy

For teams about to build. We work through what your platform actually needs — which APIs and services should exist, where the boundaries between them fall, what to build versus buy, and how tenancy and access should work across all of them — and produce an architecture and delivery sequence your team can work from.

From AUD $5,000 (ex GST), depending on the complexity of your product and what it needs to support. Confirmed after an initial consultation, before any work begins. Typically delivered within two weeks. Yours to keep, whoever builds it — and if you go on to a build with us, the fee is credited against discovery.

How we approach it

Strategy work is only useful if the recommendation might be something other than what we sell. We assess the options on their merits — an existing platform, a framework, your own build, or us — and say which fits your circumstances and why. Sometimes the answer is that you don’t need what we build.

What we work through

• Platform architecture — the realistic options for how your system could be structured, where data and APIs divide across services, and the tradeoffs of each
• Build versus buy — where an existing platform or service serves you, and where your business genuinely needs its own engineering
• Tenancy — what a tenant is in your business, how hierarchy works, and how access should derive from it
• Access and identity — who and what consumes your APIs, and how permissions should be structured across users, staff and partners
• Integration strategy — how partners will consume your data, what you publish, and how third-party systems stay in sync
• Foundational technical decisions — the choices that are hard to unwind later: data store, identity approach, how services communicate, synchronous versus event-driven, deployment and hosting model
• Delivery sequence — what to build first, what can wait, and what must be right from the start

Strategy and discovery

Strategy sets the direction: what to build and how it should be structured. Discovery, which precedes a build, specifies it in detail — the models, relationships, tenants and access rules the system will be delivered against. Strategy is a useful starting point if those decisions are still open; if you already know what you need built, discovery is the right next step.