Turn a manual workflow or product idea into a usable web or mobile app. Start with the core journey, agree what the first release needs, and build from there.

ThursdayNew job
TimeCustomerJobTechnicianStatus
11:00M. OrtizWater heater replacementLuisNew, from the website
8:00R. PatelLeak under sinkDanaDone
9:30J. BrooksWater heater serviceLuisScheduledOn the way
13:00K. AdamsDrain camera inspectionDanaScheduled
Text sent to J. BrooksLuis is on the way, arriving around 9:30.

A good fit if
You have a repeatable workflow that needs better tools, a customer portal to build, or a product idea with a clearly defined user problem.
Where we start
Describe who will use the app, what they do today and the task you want to make easier. Include any existing systems it has to connect to.
What it costs
User roles, workflows, integrations, the data involved and the platform drive the estimate. A discovery phase defines a manageable first release before a larger build is priced.
How long it takes
The first release is planned around the workflows we agree and any technical dependencies. Extra features are prioritized separately, so the scope stays clear.

Your proposal lists which of these your project needs, what is included and what is priced separately.

  • Problem and scope

    Who will use the app, what they need to do, and where the first release stops.

  • User flows and prototype

    How people complete the important tasks, mapped out and reviewed as a prototype before development starts.

  • Platform recommendation

    A web or mobile approach chosen for how the app will be used and what it needs to do.

  • Application development

    The screens, data handling, permissions and integrations built to the scope we agreed.

  • Workflow testing

    The key journeys, error cases and access rules checked against the requirements.

  • Release and handover

    A plan for going live, documentation, and who is responsible for support afterwards.

Questions about app development

How is the work priced?

The estimate depends on user roles, workflows, integrations, the data involved and which platforms you need. Discovery comes first: it defines a manageable first release before a larger build is priced.

How long will the first release take?

It depends on the workflows in the first release and any technical dependencies. Features that miss the first release are prioritized separately, so the scope stays clear.

Should this be a web app or a mobile app?

That depends on how people will use it and whether it needs features specific to a device. The decision is made in discovery, before you commit to a build.

What happens after I get in touch?

Nick reads what you send and replies by email. If the project looks like a fit, the next step is a conversation about the work before any proposal.

Nick reads every message himself and replies by email to work out the next step.