Accounts, permissions, connected data and business rules change the risk, testing and maintenance. We turn the current process into a buildable scope before fixing the price.
A marketing site publishes information. An application remembers people, changes data and makes decisions inside a workflow. Once the project needs accounts, permissions, relational records, private dashboards or actions with operational consequences, it needs application discovery and testing.
We map:
The useful starting evidence is often the spreadsheet or manual process being replaced, not a feature wishlist.
A defined workflow, data model, screen and integration scope, acceptance criteria, delivery stages, maintenance owner and fixed proposal for the build. Where a suitable existing product can do the job for less, we will recommend it instead of custom software.
Applications need monitoring, dependency updates, backups and support. The responsibility can stay with UltraLabs, your team or another provider, but it is named before launch. Monthly support is separate from the build.
Scoped after discovery
Software, not a site
From £4,000From $5,200
Authentication, application behaviour, relational data, private merchant tooling or a custom Shopify app. Requirements beyond what a marketing site or a theme can hold.
Starting price · scoped after discovery
One bounded piece
£1,500$2,000
One bounded improvement: landing pages, a template rebuild, an analytics implementation, or a build-readiness review credited against a larger project.
Fixed price
Monitoring, updates and capacity
Per month
From £1,250From $1,650
A live improvement programme on one site. You set the priorities each month, we work the queue in order, and the month closes with what changed and what it did.
Starting price
Per month
From £3,000From $4,000
Continuous delivery across an agreed portfolio, with planning ahead of the work rather than a queue you have to keep feeding.
Starting price
Applications are not instant-priced. Discovery is quoted on its own and credited against the build, because a fixed price offered before the data model exists is a number chosen for its persuasiveness.
After discovery, usually yes for a defined first release. Before discovery, no. A fixed price quoted from a written brief is either padded heavily or destined for a difficult conversation, and neither serves the project.
Sometimes not. A configured off-the-shelf tool, a spreadsheet with a proper process, or a small addition to a system you already run can be the better answer. We would rather say that than build something that duplicates a product you could subscribe to.
You do, on the terms set out in the agreement, and it lives in a repository you control. Nothing is held in an account only we can reach.
Applications need monitoring, dependency updates, backups and support. That is agreed as part of the project: it can be our ongoing responsibility, your team’s, or a third party’s, but it has to be somebody’s and it should be named before launch.
Show us how it runs now, where it goes wrong and who has to touch it.
