Skip to content

Gridsmith

Gridsmith Digital 00 / Input

When one thing changes,
the right things follow.

From the first visit to the work after launch, we build websites, software, apps and connected workflows around clear decisions and handoffs.

Route map

Follow the request.

A request enters, moves through the parts it needs, reaches a decision and returns a response; each group handles a different part of that journey.

01 / Web

Help people find their next step.

A visitor arrives with a question or a task. The site should make the next step clear, whether that is finding information, making an enquiry or using a service. We shape pages, content structures and web applications around those journeys, then agree how the site will be edited and run.

One content structure
  1. Title
  2. Body
  3. Media
  4. Action
  5. Navigation
Choose a layout
NavigationTitleBodyMediaAction

02 / Software

Make the rules of work clear.

A process depends on rules: who can see a record, who can change it, and what happens when its status moves. We make those rules explicit before building tools, portals and dashboards. That gives people using them a way to follow the work and spot where it needs attention.

Example recordRules / permissions / state
Change the record state
Record
Status
OpenIn reviewSettled
Owner
Assigned
Due
Defined
Access
Scoped
Available action

Edit permitted

Change awaits a decision

Read the settled record

State determines the next action

03 / Apps & Interactive

Let people act and see what happens.

Some work happens in the hand, on the move or through direct interaction. We decide what an app or interactive experience needs to show, accept and return. The format follows the job, from a mobile task to a game mechanic, with feedback people can understand as they use it.

Move the object

Left position confirmed.Centre position confirmed.Right position confirmed. Next input is clear.

04 / Automation & Intelligence

Pass work on with a clear decision.

A useful handoff has a clear trigger, a known destination and a way to handle uncertainty. We map those decisions before connecting systems or automating steps. Where a model is involved, its task and limits are defined, with a person kept in the decision where the result has consequences.

What happens to the request?

This is an illustration, not a live system. Rules, human checks, retries and recovery are designed for each project’s agreed scope.

  1. 01Rule matched
  2. 02Step run
  3. 03Response confirmed
  4. 04Settled

The example request has what it needs and reaches a confirmed result.

  1. 01Rule checked
  2. 02Sent for review
  3. 03Person decides
  4. 04Settled

The request waits for a person’s decision before it can continue.

  1. 01Handoff attempted
  2. 02No response
  3. 03Queued for retry
  4. 04Response received

The example holds the request, retries the handoff and shows when it receives a response.

05 / Operate & Improve

See what needs attention next.

Launch changes what needs attention; it does not end the work. Updates, monitoring and improvements are agreed for each engagement, along with who handles hosting and access. When something fails, the people responsible need enough information to find it, respond and decide what to improve next.

System observationQualitative states
Exception detected
ObservingException identifiedResponseSettled
Inspect the exception

Recovery and improvement follow the agreed responsibilities.

Engagement route / process

A clear route through the work.

Each project follows the same six stages. The detail is agreed for the work at hand.

  1. Consultation

    Understanding the business, project goals, target audience, and current digital presence

  2. Planning & Scope

    Clear project scope, timeline, pricing structure and required deliverables prepared before work begins

  3. Approval & Start

    Work begins once scope is confirmed and the agreed initial payment is received

  4. Design, Development & Updates

    The project is developed with regular updates, feedback opportunities and clear communication throughout

  5. Delivery

    Final deliverables reviewed, completed and provided according to the agreed scope

  6. Support (if applicable)

    Ongoing support, maintenance, SEO improvements and digital assistance where required

The six stages in full

Settled system / contact

The next request starts here.

Tell us what needs to connect, change or recover. We can discuss whether it fits and set the work and its arrangements out in writing.

Discuss Your Project

We typically respond within 48 hours.

Your project agreement sets out the source code, documentation, account access and handover included in the work. We prefer arrangements you can access directly, with hosting and access agreed before work begins. We agree what is needed to run and support the system after launch.

Some of our work cannot be shown publicly, either because we do not hold permission to publish it or because it is confidential. Relevant examples may be discussed privately where we are permitted to share them.

Gridsmith Digital is a trading division of Gridsmith Ltd.