Whole software,no fractions.

integer3 designs, builds and runs custom software, AI agents and cloud platforms for teams that need the whole thing to work.

Start a projectSee the work

We design the product, build the platform, wire in the agents and run it, as one team.

What we build

From brief to live

What are you building?
Two weeksDiscover. First, we map users, data and risks.One weekDiscover. First, we pick one workflow and its data.Two weeksDiscover. First, audiences, platforms and scope.Two weeksDiscover. First, an audit of what runs where.
Three weeksDesign. Then flows and UI, tested with users.One weekDesign. Then tools, guardrails and evaluations.Four weeksDesign. Then prototypes on real phones.Two weeksDesign. Then the target architecture and costs.
Twelve weeksBuild. Next, two-week releases to staging.Five weeksBuild. Next, a pilot with real users.Ten weeksBuild. Next, weekly test builds.Eight weeksBuild. Next, move service by service.
OngoingScale. Finally, launch, measure and grow.OngoingScale. Finally, more workflows, measured.OngoingScale. Finally, store launch and updates.OngoingScale. Finally, on-call, tuning and savings.
  1. Discover. First, we map users, data and risks.Discover. First, we pick one workflow and its data.Discover. First, audiences, platforms and scope.Discover. First, an audit of what runs where.
  2. Design. Then flows and UI, tested with users.Design. Then tools, guardrails and evaluations.Design. Then prototypes on real phones.Design. Then the target architecture and costs.
  3. Build. Next, two-week releases to staging.Build. Next, a pilot with real users.Build. Next, weekly test builds.Build. Next, move service by service.
  4. Scale. Finally, launch, measure and grow.Scale. Finally, more workflows, measured.Scale. Finally, store launch and updates.Scale. Finally, on-call, tuning and savings.

Typical durations from discovery call to launch. Your project gets its own plan.

Agents that ask first.

Every tool call is logged, every risky step waits for a person, and every run can be replayed.

Tools we stand behind

Rear of a data-centre server rack, with bundled network cables running between machines
Stack: technologies we use and what for
AreaToolWhat for
Front endTypeScriptOne typed language from database to browser
Next.jsWeb apps and sites, rendered at the edge
MobileReact NativeiOS and Android from one codebase
Back endNode.jsAPIs, workers and integrations
GraphQLTyped APIs between every client and server
AIPythonData pipelines and model tooling
Anthropic ClaudeReasoning and tool use inside agents
pgvectorSearch over your own documents
DataPostgreSQLThe system of record
RedisQueues, caching and rate limits
CloudAWSCompute, storage and networking
VercelServerless hosting for web front ends
TerraformInfrastructure defined as reviewed code
DockerIdentical builds from laptop to production
QualityGitHub ActionsTests and deploys on every change
PlaywrightEnd-to-end and accessibility tests
SentryErrors and performance in production

Start a project

Leave and we'll

A person replies within one working day. Prefer detail? Use the full brief form.