info@spacexit.com Contact us

How we work

Four steps. Nothing hidden in a “phase two”.

We start with the people who will use the product. Then we agree the work in writing, design it so you can click it, build it in the open, and launch with a checklist.

Design workshop mapping product flows
01

Discover

Discovery is interviews, a look at the current site or spreadsheet, and a written brief. We talk to operators, not only to the person who commissioned the work. You leave knowing the scope, the risks, and what we would not build.

You leave with

  • Written brief and user map
  • Scope and out-of-scope list
  • Rough timeline and commercial options
02

Design

We prototype the important paths (enquiry, checkout, the daily staff task) and agree them in writing. Visual design follows. If something is wrong, it is cheaper to change it here than in week eight of build.

You leave with

  • Flows, wireframes and UI
  • Clickable prototype of the core paths
  • Signed-off screen list for build
03

Build

We ship to a staging URL you can share. Content, integrations and edge cases are handled in the open. You get regular demos, not a silent six weeks. Source lives in a repo you own from day one.

You leave with

  • Working staging environment
  • Regular demos and a visible backlog
  • Source in your repository
04

Launch & support

Launch covers DNS, stores, redirects, analytics and a person watching the first days. After that, a warranty window for defects, then a retainer or a statement of work for the next slice. You always know who to email.

You leave with

  • Launch checklist and cut-over plan
  • Handover: credentials, runbook, source
  • Warranty period and optional ongoing work

What we need from you

An honest picture beats a polished one. Time with the people who will use the product, examples of what “good” looks like, and an hour with whoever signs the work.

  • Access to the current site, app or spreadsheet the new work replaces
  • Brand files if you have them. We will not invent a second logo
  • A list of must-haves versus “would be nice”
  • A named decision-maker so design does not stall in a group chat

Typical first 30 days

  1. Week 1 Discovery: users, constraints, written brief.
  2. Week 2 Scope and commercial options. No build starts without a yes.
  3. Week 3–4 First flows and UI. You click the product before we write production code.

Ready to talk about a product?

Tell us what you want to launch. If we are not the right fit, you still leave with a clearer brief.

Start a project