Built in weeks, not quarters, and it is yours from day one.
Internal tools, client portals, calculators and customer-facing apps, built with AI-assisted engineering and shipped to a fixed price and a fixed date. The code lives in your own repository from the first commit. We run our own product, LeadSignal, the same way we build for you.
- Fixed price and date, agreed before work starts
- Code in your own repository from day one
- Built and tested by the same team that runs LeadSignal in production
AI-assisted does not mean AI-generated and unowned.
A lot of software gets built fast now, and a lot of it is built badly, because speed and ownership are being treated as opposites. We build fast because AI-assisted engineering genuinely is faster, and we build it properly because a senior engineer reviews, tests and owns every part of it. Nothing ships that we would not be comfortable running ourselves.
We know that is not a claim to take on trust. LeadSignal, our own AI setter product, was built in eight weeks with the same team and the same process, has an approved Meta app, live payments and paying customers today. It is the proof that this way of building holds up once real users and real money depend on it.
Four shapes of app, one process.
Internal tools
Dashboards, quoting tools, ops systems that replace a spreadsheet or a manual process with something the whole team can rely on.
Client portals
A branded space where your customers see their own data, documents or status, wired into the CRM or systems you already run.
Calculators & configurators
Interactive pricing, ROI or product configuration tools that turn a static page into something a prospect actually uses.
Customer-facing apps
Booking, self-service and account tools built for real customer traffic, not a demo audience of one.
Scope, build, ship, in that order.
- 1
Scoping
A half-day working session to agree exactly what the app does, who uses it and what it connects to, ending in a fixed price and date.
- 2
Build
Development in short, visible cycles, with something working to look at every week rather than a silent wait for a big reveal.
- 3
Test
Automated tests written alongside the code, and a manual pass through every path a real user or customer could take.
- 4
Ship
Launched into your own hosting and repository, with documentation and a short handover session for whoever will maintain it.
Not sure which of these fits? Twenty minutes on a call usually settles it.
Three sizes, every price published.
Every project starts with scoping, so the tier reflects the real shape of the work, not a guess.
One clearly scoped tool or automation: a calculator, an internal dashboard, a single agent doing one job well.
- Scoping session included
- Automated tests around core logic
- Deployed to your own hosting
- Documentation and handover
An app wired into your CRM or other systems: a client portal, a multi-step tool, something with real integrations.
- Everything in Tool or agent
- Integration with CRM or existing systems
- User accounts and permissions
- Staff training on launch
Best for businesses needing the app to talk to what they already run
Talk about thisA multi-user platform with its own data model, roles and reporting, built the way LeadSignal itself was built.
- Everything in Connected app
- Multi-tenant or multi-role architecture
- Reporting and admin tooling
- Phased delivery with milestones
Every price excludes VAT. Run and support after launch is available separately from £450 a month.
AI writes the first draft. A senior engineer decides what ships.
AI-assisted engineering means the boilerplate, the scaffolding and much of the first pass of code is generated fast, so time goes into the parts that matter: the data model, the edge cases, the security and the tests. Every line is reviewed by a senior engineer before it ships, which is the difference between this and the vibe-coded apps we rescue elsewhere on this site.
- Automated tests around the logic that would cost money if it broke
- Authorisation and data isolation built in from the first commit, not added later
- Code in your repository throughout, never held on our infrastructure
- A named engineer accountable for the build, not a rotating team
Who this is for, and who it is not.
A good fit
- You know roughly what the app needs to do and want it built properly
- A fixed price and date matter more than an open-ended engagement
- You want to own the code and hosting outright
- The work is a defined tool, portal or app rather than an ongoing programme
Not this, yet
- You have an existing AI-built app that is breaking, see AI App Rescue
- The work is really about replacing an old system, see Legacy Modernisation
- You want an ongoing AI backlog managed for you, see Embedded AI Lead
Not sure which of these fits? Twenty minutes on a call usually settles it.
We do not ask a client to trust a method we have not bet our own product on. LeadSignal runs on the same process, the same tests and the same standards as anything we build for someone else.
What comes with every build.
Included
- A fixed price and date, agreed before work starts
- Automated tests around the logic that matters
- Code and hosting in your own name
- Documentation and a handover session
Not included
- Ongoing support after launch, available separately from £450 a month
- Scope added after the build starts, quoted as a change
Not sure which of these fits? Twenty minutes on a call usually settles it.
Questions people ask before they book.
How is this different from using Lovable or Bolt.new ourselves?
Those tools are good for a first prototype. This is a senior engineer using AI-assisted tooling to build production software, with tests, security review and ownership of every decision, aimed at real users rather than a demo.
What does a fixed price actually cover?
Everything agreed in the scoping session. If new requirements appear once the build starts, they are quoted as a separate change rather than absorbed silently or used to justify slipping the date.
Do we own the code?
Yes, entirely. It is built in your own repository and deployed to your own hosting from the first commit. We do not retain rights, access or a dependency on our infrastructure.
How long does a typical build take?
A single tool is usually two to four weeks. A connected app is four to eight weeks. A platform is phased over several months with working milestones throughout.
Can you build on our existing codebase?
Yes, if it is a reasonable foundation. If it needs stabilising first, we would say so and point you at AI App Rescue rather than building new features on unstable ground.
What happens after launch?
Run and support is available from From £450 a month, covering fixes, small changes and monitoring, or you can take the documentation and run it yourselves.
Do you use AI in the finished product, or just to build it?
Both, where it earns its place. Some builds are plain software with no AI in the finished product. Others include an agent, a chatbot or automation as the actual feature, which we scope and price the same way.
The other ways in.
AI App Rescue
For an existing AI-built app that needs fixing rather than building from scratch.
From £4,500Legacy Software Modernisation
For replacing an old Access database, spreadsheet or discontinued tool.
From £2,500Embedded AI Lead
For an ongoing backlog of builds rather than a single defined project.
From £3,500Scope it properly before anyone writes a line of code.
A half-day scoping session gets you a fixed price and a fixed date. Book a call to start it.