- We build
- Mobile apps, web platforms and the APIs, data and hosting beneath them
- We look after
- Updates, monitoring, backups and improvement on a fixed rhythm
- We work
- From Impington, Cambridge. Mon to Fri, 09:00 to 18:00 UK time
Load-bearing services
What we put in the ground
Mobile apps
iOS and Android apps, cross-platform by default, on a versioned API so app and server can change independently. Delivered with signing credentials in your accounts. Specification
Web platforms
Company sites and signed-in web applications with tested deployment, staging and a documented rollback. Static where that is stronger. Specification
Interface design
Structured UI and UX built on a component system, so new screens are assembled from tested parts rather than drawn from scratch. Specification
Publishing help
Developer accounts, store listings, privacy declarations and review handled properly, with a written release routine. Specification
Support
Maintenance, monitoring and improvement on a fixed monthly rhythm, with a short written report each cycle. Specification
Reference shelf
Plain-English notes and trusted public guidance on architecture, security and accessibility. Free to read. Open the shelf
Tool: foundations survey
Survey what you already have
Six questions we ask at the start of every takeover or rebuild. Answer honestly; nothing is sent anywhere. Where the answer is no or not sure, you will see what we would usually recommend.
Survey result
Answer the questions to see where your foundations stand.
Tool: stack builder
Sketch your stack
Planning something new? Select the layers your product needs. The section drawing updates from the ground up and lists what each layer brings with it. A planning aid, not a quote.
Approach
Foundations first
Most software problems that cost real money are not visible on the surface. They live in how data is stored, how releases happen, who has access and whether anyone can restore last week's backup. We start there, so the parts people see can be built quickly and changed safely.
That does not mean over-engineering. A small product gets a small, sound foundation. We size the structure to the load you actually expect and leave clear room to extend.
How we work
Sequence
The order we build in
| Survey | One to two weeks. We read the code, hosting, data and processes, and talk to the people who use them. You receive a written survey with risks ranked. |
|---|---|
| Drawings | Architecture notes, data model and an interface outline, written so non-specialists can follow and challenge them. |
| Groundwork | Hosting, environments, deployment pipeline, backups and monitoring set up before features, so every later change lands safely. |
| Courses | Features built in layers, each tested, reviewed and documented before the next. A working build to try every fortnight. |
| Handover | Repository, accounts and credentials in your name, runbooks for routine tasks, and a walkthrough for your team. |
From the reference shelf
Three things worth reading
- The Twelve-Factor AppOld but sound principles for software that deploys cleanly and scales without drama.
- NCSC Small Business GuidePractical, low-cost security steps from the UK National Cyber Security Centre.
- WCAG overview from W3CThe accessibility standard we build to, explained by the people who write it.
Questions
Asked at the first meeting
Will you insist on rebuilding everything?
No. Most systems have sound parts worth keeping. The survey tells us which, and we recommend the smallest change that makes the structure dependable.
Can you work alongside our own developers?
Yes. We often take the groundwork, such as pipelines, hosting and monitoring, while your team keeps building features.
What size of organisation do you work with?
Small companies, charities and teams inside larger organisations. The structure is sized to the load, so small projects stay proportionate.
How do we start?
Send a short note about what you have and what worries you. We reply during working hours, Monday to Friday, 09:00 to 18:00 UK time.
Next step
Tell us what is standing on what.
A paragraph about your product and what concerns you is enough. We will reply with questions, not a sales pitch.