Delivery process

What happens after you bring Script Forge into the work.

The process turns an initial product question into a sequence of decisions, tangible outputs and a responsible next step.

The working path

Each stage makes a different decision visible.

The exact depth and order follow the product. These are the practical outputs and client touchpoints that keep the work accountable.

01

Discovery

What we do

  • Review the business question, people affected and the current workflow.
  • Surface constraints, assumptions and the information still needed for a responsible decision.

What you receive

  • A shared problem definition.
  • Priority journeys or workflows to investigate first.
  • A visible list of risks and unknowns.

Your involvement

A focused conversation, workshop or asynchronous review of the available context.

Decision / output

Continue, reshape the question, stop, or scope the next phase with clearer evidence.

02

Scope

What we do

  • Turn the product question into priorities, boundaries and a practical sequence of work.
  • Identify what is deliberately outside the next release and where a decision depends on evidence.

What you receive

  • A prioritised scope direction.
  • Known risks, dependencies and open decisions.
  • A delivery sequence appropriate to the work.

Your involvement

Review priorities, constraints and the boundaries that protect the next useful release.

Decision / output

Agree what the next phase is responsible for delivering, and what it is not.

03

UX and architecture

What we do

  • Plan critical user flows, information boundaries and the operating context around them.
  • Connect experience decisions to data, integrations and technical constraints before implementation hardens them.

What you receive

  • A view of the priority journeys.
  • An information and technical direction for the agreed scope.
  • Questions that need validation before building further.

Your involvement

Review the critical journeys and the trade-offs that affect people, operations and delivery.

Decision / output

Choose a product and technical direction that is clear enough to design and build.

04

Design and prototype

What we do

  • Create the interface direction and test the important interactions before they become expensive to change.
  • Use prototypes to make behaviour, hierarchy and edge cases easier to discuss.

What you receive

  • A usable visual direction for the priority flows.
  • Reviewable prototypes or interaction definitions where they add useful evidence.
  • Clearer decisions for the build stage.

Your involvement

Review the important screens and interactions against the agreed product question.

Decision / output

Confirm the experience direction and resolve the decisions that affect implementation.

05

Build

What we do

  • Implement the agreed product in reviewable increments.
  • Keep integrations, data boundaries and delivery constraints visible as the system takes shape.

What you receive

  • Working product increments.
  • Visible progress against the agreed scope.
  • A clear record of decisions that changed during delivery.

Your involvement

Review working increments and make timely decisions when new evidence changes a priority.

Decision / output

Prepare a product increment that is ready for quality checks and launch decisions.

06

Quality assurance and launch

What we do

  • Test functionality, accessibility, performance, security considerations and deployment paths relevant to the scope.
  • Resolve release-blocking issues and prepare the hand-off into live use.

What you receive

  • A release-ready product increment.
  • A visible list of checks, constraints and remaining follow-up items.
  • A practical launch or hand-over path.

Your involvement

Confirm the release decision and any operational responsibilities needed for the next step.

Decision / output

Launch, hand over, or return to the relevant decision with the known constraints visible.

07

Grow

What we do

  • Use what the live product reveals to prioritise the next product, operational or technical decision.
  • Plan maintenance, improvements or the next release only where an ongoing engagement is in scope.

What you receive

  • A clearer next decision and candidate priorities.
  • An agreed path for maintenance or continued product work when applicable.

Your involvement

Review what changed after launch and decide whether another focused phase is useful.

Decision / output

Continue with a defined next scope, maintain the delivered product, or close the engagement responsibly.

Outputs are selected for the scope. A focused engagement may not require every artefact or every stage.

Delivery process

Each stage makes a different decision visible.

The process turns an initial product question into a sequence of decisions, tangible outputs and a responsible next step.

Product motion

From an ideato a productthat movesthe business.

Explore four decisions that turn uncertainty into a clear, buildable and useful system.

Discuss a projectView case studies

Delivery process

Start with the decision in front of you.

A concise brief about the product, process and current constraints is enough to begin the conversation.

Discuss a project