Process

Clear stages. Visible progress. No mystery build.

OpsForm is a UK custom software business based in Brighton. Every engagement is structured so you know what is being solved, what is in scope and what happens next.

01

Discover

We map the current workflow, users, pain points, rules, exceptions and constraints. The aim is to understand the operational problem before prescribing technology.

  • Existing tools and handoffs
  • Business rules and edge cases
  • Users, permissions and responsibilities
  • Success criteria
02

Design the first release

The workflow becomes a practical build plan: screens, data, permissions, integrations and what deliberately stays out of version one.

03

Build in reviewable stages

Work is broken into focused milestones so progress can be demonstrated and corrected early rather than hidden until the end.

04

Test the real workflow

Testing covers the happy path and the awkward operational cases—permissions, validation, mobile use, failures and the actions staff take every day.

05

Launch and hand over

Production configuration, deployment, data preparation and operating guidance are handled as part of the launch plan agreed for the project.

06

Improve from real usage

Once the software is live, support requests and improvement ideas become prioritised changes rather than uncontrolled additions to the original scope.

Project controls

Scope protects both sides.

Written scope

Core features, assumptions, dependencies and exclusions are written down before a fixed-price build is accepted.

Change requests

New ideas are assessed separately so they can be quoted, deferred or exchanged for other scope deliberately.

Acceptance

Milestones and testing criteria create a shared definition of when a feature is ready.

Your involvement

Fast decisions keep projects moving.

The best projects have one client-side decision-maker who can answer workflow questions, provide access to required services and review milestones promptly.

Nominate the main project contact.
Provide access to relevant systems and test accounts.
Review working milestones against the agreed workflow.
Flag changes early rather than at final handover.

Have a messy process but no specification?

That is exactly what discovery is for.

Plan the first release →
Beyond the build

A good launch has no loose ends.

These are the practical details to settle in the proposal, so everyone knows what ready means.

01

Your data, in good order

Agree what to import, who cleans it and how to check the result. Plan a sample migration before switching over.

02

The right access

Define who can view, change, approve and export records. Test real roles and exception cases before launch.

03

A practical handover

Confirm training, documentation, account ownership and source-code arrangements in the agreed scope.

04

A plan for day two

Set out hosting, backups, monitoring and support responsibilities, including recurring costs and response expectations.

Explore support & maintenance →