Skip to content
05Applications

Approvals and handoffs without the chasing

The steps a job goes through, written down once and run by the system: who does what next, what they need, and what happens when they do not. Nothing waits in an inbox.

Get a quote
See the catalogue
Build time
4–20 weeks
Per project
Quoted
Steps left to memory
0
01Client Portals02Internal Dashboards03Inventory Systems04Custom Databases05Workflow Tools06Management Systems
Who it is for

You will knowif this is you.

01Work stalls because somebody is waiting for a yes that is sitting in someone else's inbox.
02The same information is typed into a form, then an email, then a spreadsheet, then the accounts.
03Onboarding a customer, a hire or a supplier is a checklist that lives in one person's head.
04Things get missed at handover: between sales and delivery, between the site and the office.
What it does

Everything the systemtakes off your desk.

Each capability is built to your process and shipped with its own controls. Nothing generic is bolted on.

01

Process, written down

Each workflow is a set of steps with an owner, an input and an outcome. Drawn with you, then run by the system.

  • Steps with owners and deadlines
  • Conditions and branches
  • Parallel steps
  • Versioned: change it without breaking running jobs
02

Approvals

A request goes to the right person with what they need to decide, and a record of the decision.

  • Single and multi-level approval
  • Approve from email or phone
  • Delegation when someone is away
  • Decision log
03

Forms and intake

Work starts from a form, not a phone call, so every step after it has the information.

  • Forms with required fields
  • Public, staff or customer forms
  • File attachments
  • Duplicate detection
04

Automation

The steps that need no judgement happen on their own.

  • Emails, messages and documents generated
  • Records created in other systems
  • Scheduled and triggered actions
  • Integrations by API and webhook
05

Deadlines and escalation

A step that stalls is chased by the system, then escalated. Nobody has to remember.

  • SLAs per step
  • Reminders and escalation
  • Out-of-hours handling
  • Overdue dashboard
06

Visibility

Where every job is, who has it, how long it has been there.

  • Board and list views
  • History per job
  • Bottleneck reporting
  • Audit trail
One job, end to end

How a workflowruns.

Take a customer onboarding. Today it is eleven emails. Run as a workflow it is five steps and nobody chases anyone.

01IntakeThe customer completes a form. The job exists, with everything the next step needs, and a reference number.
02CheckThe office confirms the details. Anything missing goes back to the customer automatically with a list of what is needed.
03ApproveA manager approves the quote from their phone. If they have not by Thursday, their deputy is asked.
04DoThe job is scheduled, the engineer is notified, the documents are generated and sent. Three steps, no typing.
05CloseSign-off recorded, invoice raised in the accounts, the customer thanked. The job's whole history is one page.
Scope and timeline

Sized to the job,quoted per project.

Three sizes from the catalogue's application tiers. Start with the one process that hurts most.

01

Single workflow

Quoted

4–6 weeks

  • One process mapped and built
  • Forms and approvals
  • Email notifications
  • Board and history
  • Basic integrations
  • Staff training
Get a quote
02Most popular

Business workflows

Quoted

8–12 weeks

  • Several processes
  • Role-based access
  • Escalation and SLAs
  • Document generation
  • Integrations with your systems
  • Reporting
Get a quote
03

Advanced automation

Quoted

12–20 weeks

  • Complex branching logic
  • Multi-team handoffs
  • Customer-facing steps
  • API and webhook platform
  • Custom reporting engine
  • Change management
Get a quote

Timelines are the ones in the catalogue. The quote fixes the scope, the price and the delivery date before work starts.

Built on the platform

Workflows area Lounge module.

The platform ships a visual workflow builder for triggers, steps and actions, with an Automations Pro add-on for scheduled and cross-system runs. A custom workflow tool starts from it when the fit is close, and adds the forms, screens and integrations your process needs.

What you own

Yours outright, on the day it launches.

  • The process maps and the system that runs them, as source code
  • Every form, template and integration
  • Admin training: how to change a step without a developer
  • A support period written into the quote
  • The full history of every job that ran through it

The same terms as every build: read ownership and handover.

How it is built

Four stages, no surprises.

Whole buildSet in your proposal

01

Discover

Starts when you say go

We map how the work gets done today.

What happens

  • Workshops with the people who will use it
  • Your current process mapped, step by step
  • Your data and the systems it lives in audited
  • A written specification of what to build first

What you get

  • The specification
  • A staged plan and a fixed quote

What we need from you

  • Time with the team who do the work
  • Access to the tools you use now
02

Design

After you approve the specification

A clickable prototype before a line of code is written.

What happens

  • Screens and user journeys for each role
  • A clickable prototype the team can try
  • The data model and the integrations agreed
  • Permissions: who can see and change what

What you get

  • The prototype
  • The agreed data model

What we need from you

  • Feedback from real users
  • Sign-off on the prototype
03

Build

After you approve the prototype

Built in stages, with a working demo at the end of each.

What happens

  • Features built in the agreed order
  • A working demo at the end of every stage
  • Your existing data moved across and checked
  • Tested against the real process, not a script

What you get

  • A working system at each stage
  • A test environment to try it in

What we need from you

  • Testing time from your team
  • Decisions when questions come up
04

Launch

After you approve the finished build

Rolled out, taught and supported.

What happens

  • Rolled out to the team, in stages if that suits
  • Training for each role
  • Documentation for how it works and how to run it
  • Support after go-live, with a retainer if you want one

What you get

  • The live system
  • Full ownership of the code and data

What we need from you

  • A go-live date that works for the business
Straight answers

Asked beforeyou ask.

01Is this Zapier?Zapier connects two apps when something happens. A workflow tool runs a whole process with people in it: approvals, deadlines, handoffs and a record. The two can work together.
02Can we change a process after launch?Yes, and without losing running jobs: each job carries the version of the process it started on. Simple changes are made by an admin; structural ones by us under the maintenance plan.
03What if someone does not respond?The step has a deadline. Reminders go first, then escalation to whoever you named, then a flag on the overdue dashboard. The job never disappears.
04Can customers be part of a workflow?Yes. Forms, approvals and document signing can be customer steps, delivered by secure link or through a client portal.

Write the processdown once.

Describe one process as it actually happens today, emails and all. The quote covers turning it into steps that run themselves.

Get a quote
Talk it through first
04 · PreviousCustom Databases06 · NextManagement Systems