Process

A clear path from idea to launch.

A tangible outcome at every step. A clear decision before the next.

01 · Discover

Define what matters.

A brief and a system map.

We start with you, not with screens. We walk the work as it runs today: the tools, the hand-offs, the booking retyped twice. Discovery ends with the real problem behind your brief, in writing, and a map of the systems the work has to connect to.

Project brief · Intake platform

Illustrative sample · Fictional project
Client
Nordwind Physio (fictional)
Prepared with
Jonas Ritter
Status
Approved before design

Problem

Enquiries arrive by phone, through the website form and by e-mail. Reception retypes them into a spreadsheet and a calendar, and nobody can see which ones are still waiting for an answer.

Users

  • The reception team of three, who take every enquiry
  • The practice owner, who decides what the practice takes on
  • One coordinator, who books first appointments

Constraints

  • The existing calendar stays in place.
  • No patient health data in the new system.
  • A two-language interface for the reception team.

Scope

  • Intake form
  • Enquiry list with review states
  • Follow-up drafts that a person reviews before they leave
  • Project view for accepted enquiries
  • Reporting, in a later slice

Out of scope

  • Billing
  • Medical records

Risks

  • Adoption at reception during busy hours
  • Double entry while the old spreadsheet is still in use
  • The tone of follow-up messages

Success criteria

  • Every enquiry is visible with an owner and a state within a day.
  • No enquiry is retyped.
  • A person reviews every follow-up before it leaves.
  • Reception finds the next action in one click.

System map

  1. New
  2. In review
  3. Replied / Scheduled
  4. Project
Enquiry, review, project: the states every enquiry moves through in the Workspace.

Outputs

  • Operator interviews
  • System map
  • Risk inventory
  • Sharpened brief with success criteria

Your part

The people who do the work, for a few hours. The owner for the decisions.

Checkpoint

You sign off the brief before anything is designed.

02 · Design

Make it tangible.

A prototype you can explore.

We shape what your customers see and the layer beneath it in parallel. We pick the riskiest assumption and design the cheapest way to test it. You review working pages in your browser, never a folder of mock-ups.

Outputs

  • Clickable prototype
  • Experience and data-flow map
  • Architecture sketch
  • Build plan

Your part

A review every week, in the browser.

Checkpoint

The prototype and the build plan are approved together.

03 · Build

See progress take shape.

Working software. Shared reviews.

Production-grade from the first commit. You click through the real thing every week, so there is never a stretch where you wonder what is happening. Wherever AI is involved, it is tested against agreed examples before it ships.

Weekly demo 6 · Intake platform

Illustrative sample · Fictional project
Date
13 October 2026
Present
Jonas Ritter, the practice owner, the reception lead
Increment
Enquiry drawer and reviewed follow-up drafts

Acceptance scenarios

ScenarioObserved
A new web enquiry appears in the list with an owner and a state within a minute.Appears as New, owner assigned by rule.
A follow-up draft waits for a person before it is sent.Draft shown as In review; sending stays disabled until a person approves it.
After approval the enquiry moves to Replied and the activity shows who approved it.As expected.

Unresolved

The owner filter resets when switching between Enquiries and Projects.

Open · Owner: Jonas Ritter · Due: next demo

Next decision

Accept this slice and schedule the filter fix into slice 7, or hold acceptance until it is fixed. The decision belongs to the client.

Illustrative review. Not a real test report.

Outputs

  • Weekly demos
  • Evaluation suite where AI is involved
  • Production deploys
  • Monitoring

Your part

Weekly demo, scenarios from your team, decisions as they come up.

Checkpoint

Each slice is accepted against the scenarios before the next one starts.

04 · Launch

Make it yours.

Code, access and a clear handover.

A coordinated launch with rollback, monitoring and a runbook your team can follow. You own the repository, the accounts and the data. We stay on call for 30 days, and continue on a retainer only if you want us to.

Handover · Intake platform

Illustrative sample · Fictional project
Client
Nordwind Physio (fictional)
Planned for
17 November 2026

Code

  • Repository transferred to your organisation
  • Main branch protected
  • README, architecture records and setup guide
  • CI green on the handover commit
  • Our write access removed

Example checklist for a fictional project. It names no real account, address or system.

Outputs

  • Launch checklist
  • Runbook and alerting
  • Handover of code, access and documentation
  • 30 days on call

Your part

Your go-live decision, your release process, your team on the runbook.

Checkpoint

Launch review after 30 days: what to keep, what to tune, whether to continue.

Timing follows the scope.

  • MVP

    A focused MVP can be ready in two weeks.

  • Launch

    A scoped product can launch in around two months.

  • Discovery Sprint

    Two weeks on its own, when the idea is still open.

We agree the timeline after reviewing your requirements.

Your code. Your accounts. Your data.

You own the repository, the accounts and the data. We set everything up in your name and hand it over documented.

See the handover

Bring the idea. Let's shape the next step.

One conversation to start. Scope, timeline and price in writing before you commit.

Start a project