WEIXLABSSHEET 1 OF 9
We build
your software
and keep it
running.
Most companies hire one team to build their web and mobile apps, and another to run the cloud underneath, then spend their time translating between the two. We do the whole job: plan it, design it, build it, test it, release it, and run the infrastructure it lives on. Same engineers, the whole way round.
45 minutes with the people who would actually do the work. No sales rep in between.
We use AI heavily, and a human reads every line of it. How we use AI →
Every circle is a link. Blue is what we run; the gold is your work moving round.
WHAT WE BUILD
- Web applications and internal tools
- Mobile apps, iOS and Android
- APIs and the back end behind them
- Data models, storage and integrations
WHAT WE RUN
- Cloud infrastructure, written as code
- DevOps: pipelines, environments, releases
- Monitoring, alerting and on-call
- Security, access control and cloud cost
SHEET 2 OF 9GENERAL NOTE
We use AI.
We do not vibe-code
your production system.
Both halves of that matter. A team not using AI in 2026 is slower than it needs to be and is charging you for the difference. A team letting a model write straight into production is selling you code nobody in the building understands. We are neither.
WHERE WE USE IT
- Reading unfamiliar code fast when we inherit a system
- First drafts: scaffolding, boilerplate, test coverage, migrations
- Writing the documentation engineers never get round to
- Research: comparing approaches before we commit to one
WHERE WE DO NOT
- Architecture. That is a judgement call with your money on it
- Anything touching payments, personal data or access control, unreviewed
- Infrastructure changes a model cannot be asked to roll back
- Merging code no engineer on the team can explain out loud
WHAT THAT MEANS FOR YOU
- You get the speed, at the price the speed should cost
- Every line in production has been read by a person
- That person is the one holding the pager at 3am
- Nothing in your system is a black box we cannot explain
THE TEST WE APPLYIf an engineer here cannot explain a change out loud, in plain words, it does not ship. That rule does not care whether a person or a model wrote it.
SHEET 3 OF 9PHASE 01
Plan
Before anyone writes a line, we survey what you already have. Your code, your cloud account, how changes reach your users today, what broke last month. Half the value of this phase is finding the things you do not need to build.
- Reading your existing system, honestly (AI helps here, a lot)
- Deciding what to build and what to leave alone
- What it will cost to run, per month, before you commit
- Where the real risk sits
YOU END UP WITHA map of what you have, and a shortlist of what to do about it, whether or not you hire us.
SHEET 4 OF 9PHASE 02
Design
This is where most projects quietly go wrong. The app gets designed by one company and the cloud it runs on by another, months apart. We draw both on the same sheet, in the same week: the web and mobile side, and the infrastructure and DevOps underneath. Press the buttons to see what each half looks like alone.
YOU END UP WITHAn agreed plan for both halves, signed off before the build starts, with the monthly running cost written on it.
SHEET 5 OF 9PHASE 03
Build
Not the screens first and the plumbing at the end. Every week we finish one narrow slice that goes all the way down: screen, logic, data, and the thing it runs on. Then we put it somewhere real. You are never looking at a demo.
- Web apps, mobile apps and the APIs behind them
- Cloud infrastructure written as code from week one
- Connecting the tools you already use
- One finished slice at a time, live in a real environment
- AI to move faster, an engineer to read every line of it
YOU END UP WITHWorking software every week, in an environment you can open and click.
Point at a week to see what goes out in it.
SHEET 6 OF 9PHASE 04
Test
Every change goes through the same four gates, automatically, every time. If one shuts, the change goes back to whoever wrote it, including us at five to six on a Friday.
- Automatic checks on every single change
- Scanning for known weaknesses before release, not after
- A private copy of the whole system for every change
- A person reviews it too, whether a human or a model wrote it
YOU END UP WITHA route to production that nothing broken can walk through by accident.
SHEET 7 OF 9PHASE 05
Release
New things reach a handful of users first, then more, then everyone, and only if the numbers stay healthy at each step. If they do not, it comes back out. Undoing a release takes about a minute here, because we have practised it rather than hoped.
- One release route, used by your team and ours
- A few users first, everyone last
- A way back that has actually been rehearsed
- Releases during the working day, not at midnight
YOU END UP WITHReleases that stop being an event, and a way back that you have seen work.
SHEET 8 OF 9PHASE 06
Run
This is the phase nobody wants to sell you, and the one that decides whether the previous five were worth anything. Five things stay attached to your cloud for as long as you want us there, and what they tell us becomes the next plan.
Point at a circle to see what we actually do there.
- Someone on call who has read your code
- Instructions kept next to the code, not in someone’s head
- Honest reviews after an incident, aimed at the system
- A clean handover and goodbye whenever you want one
YOU END UP WITHA system that keeps working, and a partner who is still there in month eighteen.
SHEET 9 OF 9TITLE BLOCK
Where are you
on the loop?
Tell us which phase you are stuck in and we will book 45 minutes with the engineers who would do the work. We will read whatever you can share beforehand, and we will say so plainly if what you are describing does not actually need us.