Services
Explore
Free AI assessmentAnswer 15 questions about one process and see where AI could help.
Start an assessment04 · Application Development
Software built around the way your business works
You get tested software you own, designed around your users and processes, with AI features where they do a task better.
- Azure
- Salesforce
- Shopify
- Slack
Examples
How the software is built
Examples based on client projects. Names and figures in them are illustrative.
Designed around your process
We map the process the software supports, agree the screens with the people who will use them and write down what each release must do.
Short cycles with a demo at the end
We build in short cycles. Each one ends with a demo to the people who will use the software, and their feedback sets the next cycle.
Tested on real cases before release
Automated tests run on every build, and the people who use the software test it on ordinary cases and awkward ones before each release.
- Run the automated testsOn every changeTests
- Security and accessibility checksPart of each releaseChecks
- Release to stagingA copy for your team to tryStaging
- Demo to your teamThe people who will use itDemo
You own the code and the documentation
At handover you receive the source code, the documentation and the access details, so your team or another supplier can run and change the software.
Overview
What Application Development means in practice
You get working software, the code and the documentation to run it.
We design, build, test and hand over software for your business, from the screens to the hosting and data. Clear structure and automated tests mean your own engineers, or another supplier, can maintain it. Like most software, it relies on hosting and third-party libraries, which keep their own licences.
What you receive
- 01Software in use
Tested, deployed software, monitored after launch.
- 02Code and access
Source code, documentation and access details passed to your team on completion, under the terms of your agreement.
- 03Code your team can maintain
Clear structure and test coverage that your engineers can build on.
- 04Documented handover
A written handover, with support after launch if you want it.
You own the code we write for you. Before any code is written, a written proposal sets out the plan, price and timeline.
Talk to usScreens to hosting, one team
We build the front end, back end, cloud hosting and data pipelines an AI application needs.
Progress you can see
Short cycles each end with a demo, so you see what has been built, what comes next and why.
Code you own
We document and test what we build and hand it to your team with the access and knowledge to run it.
At release
A release report your team can check
Each release lists what changed, what was tested and what the users should know, before it goes live.
Example document. Names and figures are illustrative.
How it works
How we deliver Application Development
Step 1 of 4
Design
We agree the structure, how users move through the software and the technical trade-offs with you before writing code.
Should we use a no-code platform instead?
For a simple tool, often yes, and we will say so. For software your business depends on, we design the structure, security and tests, and an engineer reviews any AI-generated code before it is used.
Which technology do you use?
Mostly React and TypeScript for front ends, Node.js or Python for back ends, and PostgreSQL or cloud databases. We work with your existing systems where that suits the project.
How long does a project take?
It depends on the size of the plan and the systems involved. You get an estimated timeline, with the assumptions behind it, before any code is written.
Who owns the source code?
You own the source code we write for you, and we hand over documentation and access on completion. Third-party libraries and services keep their own licences.
What happens after launch?
Either we support and maintain the software with agreed service levels, or we hand it to your team with documentation and training. We agree which before the build begins.
How do you handle security and data protection?
We follow recognised security practice, such as the OWASP (Open Worldwide Application Security Project) guidance, with data classification, encryption in transit and at rest, and access controls. We agree the rules that apply and the checks with you before anything goes live.
How is the project priced?
We write the plan first. The proposal then shows the price and what it covers before we start.
What kinds of software do you build?
Internal AI assistants, workflow tools, customer-facing AI products, data pipelines, client portals, practice management systems and connections between your systems. Send us a short description if you want to check your idea.
Also from Reformat Labs
Explore our other services
For teams starting with AIAI WorkshopsPractical sessions where your team uses AI on its own tasks and learns what needs checking.
For tasks your team repeats every dayAgent DeploymentsAI agents that carry out agreed steps across your tools, with a named person approving their work.For deciding what to buildAI ConsultancyA written plan of which tasks AI can take on in your business, what each would cost and which to start with.
For tools your team already relies onManaged ServicesSupport, monitoring and improvement for the AI tools and applications your team relies on, with a monthly review.Talk to us
What should the software do?
Bring the process the software should support and the systems it must work with. We will tell you what we would build first and why.