Service 04 / 05Typical: 6–10 weeks

Software& SaaS

We start with the job the product has to do, prove it with a clickable prototype, then build in short increments you can use and test as we go.

Typical MVP6–10 weeks after scope
PricingFixed per increment, quoted up front
CadenceTwo-week increments with a demo
You receiveSource code, deployment and documentation
01 — Lifecycle

From idea to release.

Week 1

Discover

Scope the core workflow and what is left out.

Weeks 2–3

Prototype

A clickable prototype, tested with real users.

Weeks 4–9

Build

Working software every two weeks, with a demo.

Week 10

Release

Testing, deployment and handover.

02 — MVP planner

Plan your MVP.

Tick what your first release must have. We lay it out in two-week sprints.

03 — Architecture

What we build on.

Client

  • Web app
  • Mobile app
  • Admin panel

API

  • Authentication
  • Business logic
  • Integrations

Data

  • Database
  • File storage
  • Backups
Managed cloud hostingMonitoring and alertsAutomated testsDocumentation
04 — What you get

Software built outward from the workflow.

Product brief and scope

The user, the problem, the core workflow and what is deliberately left out of version one.

Clickable prototype

Tested with real users before expensive development begins.

MVP build in increments

Working software every two weeks, deployed to a staging link you can use.

Testing and release

Functional testing, device checks and a managed first release.

Documentation and handover

Technical and user documentation written as part of the build, not afterwards.

Two revision rounds

Consolidated feedback, fixed promptly, included in every quote.

05 — Schedule

The schedule, drawn to scale.

Plan
Day00
Typical schedule. Your quote states the dates.Launched
WorkReview / scopingLaunch
06 — Fit

A good fit if

  • You have a specific workflow or user problem to solve
  • You can make product decisions within a few days
  • You want documentation and source code included

Not the right service if

  • You want a large platform scoped in a single meeting
  • You need a full team of engineers on retainer
07 — Questions
What do you build with?

We choose per project. Typically modern web frameworks, mobile apps and managed cloud hosting, chosen for maintainability over novelty.

Do you build mobile apps?

Yes. Vetripen, our own safety app, is currently in development.

Who owns the code?

You do, on final payment.

Can you take over an existing codebase?

Yes, after a short review. We will tell you honestly what is worth keeping.

08 — Our own product

Vetripen, a personal safety app we are building.

Share a journey with trusted contacts, call for help in one tap, and alert your contacts. It is the same process we use for clients: define it, prototype it, test it, document it.

In development. Not an emergency service.

About Vetripen →
Start a project

Send a brief. You get a reply within one working day and a written, fixed-price quote within two.