Skip to content

How a project works

See the direction before you commit to the full build.

Discovery defines the problem. A focused free demo proves one useful part. A project contract follows only if the direction works—then we design, build, test and launch.

Request a free demo See the full process
  1. 01
    BEFORE A CONTRACT Focused demo

    One agreed part

  2. 02
    AGREEMENT Scope

    Work, milestones, terms

  3. 03
    PROJECT Build

    Design, engineering, review

  4. 04
    RELEASE Launch

    Handover and ownership

How we work

A clear path from
first call to launch.

See it before you sign. Then watch it go live.

Free demo / 01—03Direction before commitment

After the demo

A visible path from discovery to handover.

Each stage ends with something concrete to review. The exact shape changes with the project; the decision points stay clear.

  1. 01 / DISCOVERY

    Define the work around the real problem.

    We align the audience, workflow, constraints, success criteria and people responsible for decisions.

    Output · Project brief and scope map
  2. 02 / DESIGN

    Turn the scope into an experience people can judge.

    Flows, screens, content hierarchy and system behavior become visible before engineering decisions harden.

    Output · Approved design direction
  3. 03 / BUILD & TEST

    Build the system and test the parts that matter.

    We develop the agreed experience, connect the required services and run quality checks throughout delivery.

    Output · Tested release candidate
  4. 04 / LAUNCH & HANDOVER

    Release with ownership made clear.

    We complete the launch checks, transfer agreed access and give the team the documentation needed to operate the work.

    Output · Live system and handover pack

Decision rights

Choose how closely you steer.

The working mode changes the amount of day-to-day involvement, not your visibility into the important decisions.

01 / CLIENT-INVOLVEDMore touchpoints

You shape each milestone.

Your team joins regular reviews and stays close to experience, content and product decisions.

DISCOVERY
Working session
DESIGN
Direction review
BUILD
Milestone review
LAUNCH
Final approval
Useful when internal expertise should guide the detail.
02 / STUDIO-LEDFewer touchpoints

We lead the delivery.

You name the goal, constraints and decision-makers. We coordinate the work and bring forward the choices that need approval.

BRIEF
Goal confirmed
DIRECTION
Client approves
DELIVERY
Studio leads
LAUNCH
Client approves
Useful when your team needs one accountable delivery partner.

Build quality gates

Quality is checked before handover.

The checks match the system. A marketing site and a permissioned platform do not need identical testing, but neither should reach launch without clear owners and release criteria.

Gate What we check Applied
01Responsive

Key screens work from phone to desktop

Every build
02Performance

Pages and interactions are tested for speed

Every build
03Access & permissions

Roles and sensitive actions are defined

Platforms
04Integrations

Connected services fail clearly and recover safely

Where relevant
05Content & measurement

Owners, events and useful reporting are agreed

Before launch
06Handover

Documentation and ownership are clear

At launch

After launch

Ownership first. Support when useful.

The agreed system, access and documentation are handed over to the people who will own them. Ongoing support, improvement or marketing can be scoped around what the work actually needs.

HANDOVER PACKILLUSTRATIVE
  1. 01Access register
  2. 02Operating notes
  3. 03Release record
  4. 04Next-step options

Common questions

Is the free demo a finished product?

No. We agree one useful screen, interaction or workflow for the demo. It is there to show the direction before a project contract, not to replace the full design, build and testing work.

What happens if the direction is right?

We turn what we learned into a written scope with the work, milestones, decision points and commercial terms. The full project starts only after that scope is agreed.

How involved does our team need to be?

That depends on the working mode. You can stay close to design and product decisions, or appoint decision-makers and let us lead delivery. Both modes keep approvals visible.

What happens after launch?

We hand over the agreed system, access and documentation. Ongoing support, improvement or marketing can be scoped separately when it is useful.