# How we work | Working Pace

Canonical: https://workingpace.com/approach
Updated: 2026-10-22

- [Home](https://workingpace.com/)
- How we work

How we work

# First, your business. Then, the build.

A practical path from understanding the work to putting a useful improvement into everyday operation. We agree on scope, success and responsibilities before building.

[Talk through a first step](https://workingpace.com/book)

## Understand your business.

We walk through real examples with your team, identify where work waits and distinguish a symptom from its underlying cause. Existing tools, permissions and data quality are part of that picture.

The output is a shared workflow, the constraints that matter and a short list of worthwhile opportunities. Discovery can reveal that configuration or a simpler process change is enough.

- A shared map of the real workflow
- The constraints, risks and opportunities to investigate

Image: The current workflow mapped across connected systems.

## Agree what to do.

Together we choose a first outcome, define the completion conditions and identify how to measure the starting point. We scope a useful release rather than a long feature wish list.

The project agreement covers deliverables, source and data access, hosting, third-party costs, ownership and support responsibilities. Exact terms depend on the engagement.

- A defined first release and a way to measure it
- Agreed responsibilities, costs, ownership and support

Image: Priorities and delivery milestones arranged into a clear plan.

## Build, launch and improve.

We test the difficult cases as well as the happy path. The team sees the work before rollout, and the release has a recovery plan and a clear owner for exceptions.

After launch, we compare the agreed measures and learn from everyday use. Support and continued development are scoped around what the business needs next.

- A tested release, rollout and recovery plan
- Team guidance and a clear route for support and changes

Image: A working software experience prepared for team use.

A little clarity

## Questions worth asking.

Do we need a technical specification first?

No. Discovery can establish the process, desired outcome and constraints needed to scope a project.

Do you offer a free build or a fixed project price?

The first conversation is to understand whether we can help. Discovery, delivery and support are agreed separately; no universal price or free implementation is implied.

Keep exploring

## A useful next step.

[What should you automate first?](https://workingpace.com/guides/workflow-automation-guide)[Build or buy business software?](https://workingpace.com/guides/build-vs-buy-software)[Carrier-request AI agent](https://workingpace.com/work/carrier-request-agent)[Talk with us](https://workingpace.com/contact)

Start where you are

## A useful first conversation.

Tell us about your business and the work you would like to improve. No finished technical brief needed.

[Talk with Working Pace](https://workingpace.com/book)

---

Contact: jake@workingpace.com
Book a conversation: https://workingpace.com/book