revsetlabs
Book a consultation

HOW WE WORK

First, your process.
Then, the build.

A clear scope, a tested customer journey, and a team that knows how to operate what we hand over.

Prepare my project brief
An illustrative business owner explaining her customer process while an implementation specialist listens and takes notes.Illustrative scene · Image details
01

Your process

We understand how the work moves.

02

Your first release

We define what the system should do.

03

Your working system

We build, test, and hand it over.

SEE IT IN PRACTICE

Know what you’re approving.

Follow a sample quote-follow-up project from the first conversation to the point your team takes ownership.

01 / 03

Start with one open quote.

Your team walks through an actual process using anonymized details: who sends the quote, when they follow up, and what counts as a decision.

A scope should describe observable behavior. “Automate sales” is too vague to approve.

THE PRACTICAL EXAMPLE
First release: follow up on approved, open quotes. Pause on replies and recorded decisions. Escalate scope or price questions.
WHAT TO LOOK FOR
  • Input: current process and tools
  • Deliverable: agreed scope
  • Approver: business owner
THE NEXT ACTION

Agree the trigger, timing, exclusions, ownership, and acceptance criteria before implementation.

02 / 03

A reply arrives before a reminder.

A sample customer reply arrives immediately before the scheduled follow-up. The old send is still waiting in the queue.

Testing the interruption is just as important as testing the happy path.

THE PRACTICAL EXAMPLE
Expected: no stale reminder. Observed: send suppressed, reply recorded, quote owner assigned.
WHAT TO LOOK FOR
  • Evidence: message and event history
  • Check: opportunity state
  • Reviewer: process owner
THE NEXT ACTION

Review the normal path, duplicate events, replies, closed quotes, and unavailable tools together.

03 / 03

Monday morning. Who checks what?

After acceptance, the team needs to know where failed actions appear and who is responsible for resolving them.

A working handover gives your team a way to operate the system after the project ends.

THE PRACTICAL EXAMPLE
Operating note: the named owner reviews exceptions, checks the latest record, and follows the recovery instructions before retrying.
WHAT TO LOOK FOR
  • Deliverable: operating playbook
  • Access: business-owned accounts
  • Support: separately agreed scope
THE NEXT ACTION

Confirm access, recovery instructions, monitoring responsibility, and the support arrangement.

Illustrative examples. No messages are sent, records changed, or appointments booked.

  1. 01

    Understand the journey.

    We review where inquiries arrive, how they move, who owns each step, and where work stops or repeats.

    YOU RECEIVE
    A current process map and one agreed problem to address.
    YOUR TEAM CONTRIBUTES
    Show us a typical customer journey and the tools your team uses.
  2. 02

    Agree on the first release.

    We define the workflow, required access, software choices, operating rules, milestones, and acceptance criteria.

    YOU RECEIVE
    A proposal with deliverables, dependencies, investment, and support scope.
    YOUR TEAM CONTRIBUTES
    Approve the business rules and assign a decision-maker.
  3. 03

    Build and test together.

    We configure the agreed environment and walk through ordinary journeys and exceptions using suitable sample data.

    YOU RECEIVE
    A configured workflow and a record of the observed test results.
    YOUR TEAM CONTRIBUTES
    Review the messages, inspect example records, and resolve business-rule questions.
  4. 04

    Launch and hand over.

    We agree the release sequence, confirm who monitors exceptions, and document how the workflow is operated.

    YOU RECEIVE
    An operating guide, ownership map, and agreed post-launch support.
    YOUR TEAM CONTRIBUTES
    Confirm the acceptance criteria and the people responsible after launch.

A PRACTICAL ACCEPTANCE STANDARD

Show what happens.
Check what changed.

A finished build should be demonstrated in the places your team actually works: the conversation, calendar, record, and next-action list.

Download the acceptance checklist
  • One normal journey reaches its agreed next step.
  • A repeated event does not create unintended duplicate actions.
  • A reply or changed decision stops the relevant follow-up.
  • An unavailable tool creates a visible issue and a recovery owner.
  • A question outside approved information reaches a person.
  • Your team knows where to inspect, pause, and operate the workflow.

OWNERSHIP AFTER LAUNCH

Ongoing work
needs an owner.

Messages change. Services change. Software changes. The scope should say who maintains the system and how requests for changes are handled.

We agree support responsibilities, escalation routes, and any ongoing commercial arrangement in the proposal. Monitoring coverage and response targets depend on that agreement.

See how support affects the scope ↗

A CLEARER FIRST STEP

What would you rather
spend your time on?

Bring the follow-up, booking, or handoff that keeps landing back on your desk. Let’s work out what a better process should do.

Book a consultation Your process. Your tools. One starting priority.See the customer journey first

Find your next answer.

Start with a topic or question.

You can also browse all field guides or the workflows.

REVSET LABS · INTRO CALL

Find a time to talk.

Scheduling is provided by Calendly. Open in a new tab ↗

Loading available times…