Custom Software
Web platforms and internal systems, specified in writing and covered by automated tests. Interface, API and data ship as one.
Engineered.
Not assembled.
Custom software for founders and CTOs: web platforms, mobile apps, APIs and cloud. A written spec first, two-week sprints, and working software you can click every Friday.
Sprint board
Sample data. 10 open items. Drag a card, or focus one and press space to move it with the arrow keys.
TLYO
- HighSPR-41
Retry failed webhooks with backoff
API31TL - LowSPR-29
Retire the v1 export endpoint
Legacy1TL - MediumSPR-14
Write the handover runbook
HandoffTL
- HighSPR-38
Move session store to Redis
Platform2TL - HighSPR-22
Cache invalidation on role change
Platform5TL - MediumSPR-33
Terraform module for staging
Infra41TL
- MediumSPR-36
Approve the orders API contract
API2YO - HighSPR-09
Sign off the key rotation window
Security41YO
- MediumSPR-26
End-to-end suite on every merge
Testing31TL - LowSPR-18
Preview deploy for every pull request
DevOps22TL
Our stack
Our stack: TypeScript, Go, Rust, Python, Swift, Kotlin, Next.js, React, NestJS, React Native, Expo, PostgreSQL, Redis, pgvector, Docker, Kubernetes, Terraform, ArgoCD, AWS, GCP, Azure, Cloudflare.
Engineered, not assembled
We write the spec first, build in two-week sprints, run automated tests on every change and hand over software that runs in production. We measure success by shipped software, not billable hours.
See what we buildEight disciplines. One technical lead.
We take software from architecture to production, with the same technical lead on it from the first call to handover.
Releases
Mobile Apps
iOS and Android in Swift, Kotlin, React Native and Expo. Native quality, with a build you can test on your own phone every Friday.
API Design
Versioned, documented contracts that web, mobile and partner systems can build against without surprises.
Cloud Infrastructure
AWS, GCP, Azure and Cloudflare. Infrastructure as code, designed for load, cost and recovery from the first deploy.
Run 001 completed · 1.2 s
AI & Automation
Workflows and AI features built into the systems you already run, using OpenAI or Anthropic where they earn their place.
DevOps & Platform
Docker, Kubernetes, Terraform and ArgoCD. Every merge builds, tests and ships a preview, with a rollback point ready.
Technical Consulting
Architecture reviews, audits and roadmaps, written up and handed to you. Tell us what you are building and we will tell you what is possible.
Legacy Modernisation
Out with the old, in with what actually works. Drag to compare a legacy screen with its rebuilt, modern replacement.
Microsoft 365 and IT
Inventixx is a Registered Microsoft Partner. We run tenant setup, migration and day-to-day IT for teams that want one accountable partner.
From spec to handover in four steps.
The same sequence on every engagement: specified before it is built, shipped in small steps you can see, covered by automated end-to-end tests, and handed over complete.
Tell us what you are buildingTechnical specificationStep 1 of 4
Scope and goalsAgreed
Architecture and stackAgreed
Data model and API contractsAgreed
Risks and unknownsAgreed
Milestones and estimateIn review
A full technical specification, agreed before any code is written. Sample outline.
Standards we hold ourselves to.
We measure success by shipped software, not billable hours. These are the commitments that sit behind every engagement.
One technical lead, start to finish.
Your technical lead is accountable from the first call to handover, for the spec, for every Friday link and for what reaches production.
Answered within 24 hours.
Every enquiry gets a written reply within 24 hours, on working days, whether you are scoping a build or chasing a fix.
Your code, your repository.
Your code lives in your repository from the first commit; the IP is assigned to you on full payment. Keys, documentation and training at handoff, and no lock-in to us.
A fortnight, in the open.
Sprints are two weeks, and a link you can open and use arrives every Friday. No client counts or vanity metrics: these describe how we work, how quickly you hear back and who owns the result.
Get a reply within 24 hours, on working daysA sample sprint
Illustrative rhythm
MonTueWedThuFriWeek 1PlanBuildBuildTestLinkWeek 2BuildBuildTestReviewLink
The link on Friday is deployed software you can use, not a slide deck.
- Sprint length
- 2 wks
- Deployable link, every week
- Fri
- Reply to every enquiry, on working days
- 24h
- Code in your repository from commit one
- Yours
Every build starts with a paid spec. The price is fixed and quoted in writing before we start, and the spec is yours to keep once paid for. It produces the technical specification and the estimate before any code is written. What the spec contains.
See your software while it is being built.
Tell us what you are building and we will tell you what is possible. You will have a deployable link to open every Friday once the sprints begin.
Your first stepFixed price
Spec first.
Quoted in writing before we start. Yours to keep if you build elsewhere.
You send the context
However rough
You get a reply
In writing, on working days
Discovery
Written spec before code
Development
Two-week sprints