The ProcessScout platform

Understand the business. Move the work forward.

A connected workspace for discovery, AI investigation, scenario planning, process design and delivery. Bring your team’s knowledge into focus and turn it into a practical change.

Create your workspace Try a tool free Explore the demo

The connected platformFrom context to action

One business context. Many useful outputs.

The journey through ProcessScout

From understanding the work to making change happen.

Discover how the business works, investigate what could be better, choose an approach and carry it through design and delivery.

01 / Recording Studio

The work tells the story.

Follow a screen walkthrough. Capture the actions, the commentary and the moment a handoff gets stuck.

Northstar / Recording StudioSimulated walkthroughMCJL

Delivery team walkthroughFictional Northstar example

Northstar CRM / Client handoffsScreen walkthrough

SALES OPERATIONS

Ready for delivery

JL

Search client handoffs September sample

Client	Scope	Delivery owner
AAlder & Co	Agreed	Unassigned
FFern Studio	Agreed	Unassigned
HHarbour Works	Agreed	Unassigned
JJuniper Group	Agreed	Jordan Lee

JL

“The scope is usually there. I open the handoff and check what Sales has sent across.”

00:00 / 00:36Captioned · silent

03 / Architecture Studio

Give the change a shape.

Explore the changes across systems, data, technology, people and processes. Sequence the work into phases everyone can see.

Northstar / Architecture StudioInteractive product illustrationMCJL

Client operations · transformation matrixFictional Northstar example

Transformation phases across columns and architecture dimensions down rows
DIMENSIONSWhat changes	PHASE 01Clarify the handoffOwners & readiness	PHASE 02Connect the workMappings & a measured pilot	PHASE 03Extend carefullyReview before expansion
Systems
Data flows
Technology
Org designPeople & roles
Processes
Outsourcing

04 / Design workspace

Work through what changes.

Design the data flows, map spreadsheet fields and keep exceptions visible. Give implementation a clear specification.

Northstar / Design workspaceInteractive product illustrationMCJL

Client handoff · target designFictional Northstar example

Client handoff / Design v0.2

Target data flowProposed · review required

SOURCE

Customer CRM

Handoff submitted

handoff_id string
client_name string
delivery_owner required

Webhook

TRANSFORM & VALIDATE

Readiness check

Map once. Keep the rules.

Preserve the source ID 01
Normalise field values 02
Require a delivery owner 03

Valid record

DESTINATION

Project workspace

Ready for human acceptance

Source reference retained
Delivery lead reviews
Brief follows acceptance

↳

Missing owner or incomplete record?

Route to the exception queue. Return to Sales for clarification.

No silent defaults

Handoff-records.csv60 fictional source records · SRC-03

Project workspaceProposed import mapping

Spreadsheet field	Target field	Transformation	Validation
`id`	`handoff_id`	Preserve source ID	Unique key
`client`	`client_name`	Trim whitespace	Required
`delivery_owner_at_submission`	`delivery_owner`	Require a named owner	18 need review
`returned_for_clarification`	`review_required`	Keep the exception flag	Boolean
`cycle_days`	`original_cycle_days`	Retain the baseline	Number

60 sample rows42 have an owner18 need clarification

Review the exceptions before any import. These are sample-data checks, not a completed migration.

The same source IDs, owners and business rules carry into the implementation specification.

05 / Build workspace

From the design to the build.

Inspect the code and connection requirements. Check sample inputs, preserve the human approval and prepare the work for review.

Northstar / Build workspaceInteractive product illustrationMCJL

Client handoff · implementation previewFictional Northstar example

1// Proposed handoff adapter · review before release2// Validation never makes the acceptance decision.34export function prepareHandoff(record) {5  const owner = record.delivery_owner_at_submission?.trim();6  if (!owner) {7    return { route: 'needs-review', reason: 'Delivery owner is required' };8  }9  if (!record.id?.trim() || !record.client?.trim()) {10    return { route: 'needs-review', reason: 'Source ID and client name are required' };11  }12  return {13    route: 'ready-for-approval',14    payload: {15      handoff_id: record.id,16      client_name: record.client.trim(),17      delivery_owner: owner,18    },19  };20}2122// Next: send valid payloads to the approval queue.23// Target credentials and access must be configured.

1{2  "source": {3    "system": "Customer CRM",4    "event": "handoff.submitted"5  },6  "destination": {7    "system": "Project workspace",8    "operation": "create_approval_request"9  },10  "mapping": "handoff.js",11  "idempotency_key": "handoff_id",12  "on_missing_owner": "needs-review",13  "acceptance": "Delivery lead",14  "credentials": "configure_in_target_environment",15  "release": "requires_review_and_approval"16}

1// These checks also run locally in this preview.2import { prepareHandoff } from './handoff.js';34// Incomplete handoffs cannot proceed.5expect(prepareHandoff({ delivery_owner_at_submission: '' }).route)6  .toBe('needs-review');78// Complete handoffs still require human approval.9expect(prepareHandoff({10  id: 'NS-004', client: 'Juniper Group',11  delivery_owner_at_submission: 'Jordan Lee'12}).route).toBe('ready-for-approval');1314// Preserve the source identifier in the payload.15expect(prepareHandoff({16  id: 'NS-004', client: 'Juniper Group',17  delivery_owner_at_submission: 'Jordan Lee'18}).payload.handoff_id).toBe('NS-004');

⑂ handoff/readiness-checkIllustrative code · review required

Explore ProcessScout

The whole picture. In working detail.

Step inside a connected workspace. Follow one business from scattered evidence to a clear decision, a better process and a practical delivery plan.

Start with Organization Brain. Explore the sources, ask a question, compare the options and inspect the work that follows.

Open the Northstar demo

ProcessScout / Northstar workspaceInteractive preview

Northstar › Client operations › Organization BrainMCJLShared workspace

Organization Brain

A living map of the people, processes and systems behind the work.

Client operations

12 entities23 relationships3 connected sourcesEvidence & proposals distinguished

Organization Brain/ NorthstarIllustrative workspace

↔ Scroll to exploreView selected details ↓

Explore the model. Select an entity to see its evidence and relationships.

Processobserved

PROC-02 / Northstar

Client onboarding

Turn an agreed scope into delivery-ready work. Follow the people, systems and evidence behind this handoff.

Accountable role: Delivery lead
State: Current process

Supporting evidence02

Connected relationships07

The missing-owner check currently happens after the handoff.

Evidence, interpretation and proposals stay distinguishable.Fictional business data · no live connections

Studio

Client operations / Handoff investigation

Project context

MC

Why does client onboarding keep getting stuck?

ProcessScoutExample analysis

The delay starts before delivery accepts the work.

In the sample, 18 of 60 handoffs arrive without a delivery owner. The walkthrough describes a return-to-Sales loop, even though the checklist requires an owner before acceptance.

18 / 60Missing an owner

8.4 daysSample mean cycle

3 sourcesOpen to inspection

A practical next step

Move the readiness check earlier. Keep a named person responsible for exceptions and let Delivery make the acceptance decision.

The sources suggest a relationship, not proof that missing ownership causes every delay.

DRAFT OUTPUTHandoff investigation

Finding: ownership is checked late
Evidence: sample + team walkthrough
Next: compare a checklist with automation

Processes

Client onboarding / From agreed scope to delivery

6 steps

Select a step to inspect its role, system and evidence.

Current step details

Human decision

Check readiness

Review the scope, approval and owner. Return incomplete handoffs to Sales for clarification.

Accountable role: Delivery lead
System: Project workspace

Supporting evidence

Opportunity to explore

Move the readiness check earlier, keep exceptions with a named owner and retain delivery acceptance.

Scenarios

One goal: a delivery-ready handoff with clear ownership.

3 options

Current-state baseline → Handoff investigation → Compare options

Fictional scenarios. All values are planning assumptions in USD.
Decision fact
Implementation	$9k	$36k	$72k
Annual running cost	$2.1k	$9k	$20.4k
Capacity released / year	540 hours	1,800 hours	2,160 hours
Net modeled value / year	$33k	$108k	$120k
Simple payback	3.3 months	4.0 months	7.2 months
Delivery estimate	2 weeks	6 weeks	12 weeks
Change risk	Low	Medium	High

OPTION B / PLANNING CASE

Automate the handoff

Check readiness in the CRM, route exceptions to a person and prepare the delivery brief after acceptance.

Balances effort and potential value. Requires field mapping, access checks and a measured pilot.

01Confirm rules & access
02Build and test the handoff
03Pilot, measure & review

Capacity value, not a committed cash saving. 720 handoffs/year × time released × USD 65/hour, less annual running cost. Simple payback uses that net value and excludes adoption ramp, tax and discounting.

Documents

Decisions, procedures and plans / Client operations

3 deliverables

Evidence → Selected direction → Reviewed deliverables

NORTHSTAR SERVICESDecision brief / v2

Reviewed

A clearer handoff. A practical next step.

Move the readiness check before the handoff. Prepare the delivery brief only when the scope, approval and owner are present. Keep the acceptance decision with Delivery.

01

What the evidence says

18 of 60 example handoffs arrive without a delivery owner. The team describes a clarification loop back to Sales.

02

The proposed change

Check the required fields, assign exceptions to the account manager and route complete work to the delivery lead.

03

How we will know

Pilot 20 handoffs. Compare cycle time and actual effort with the sample baseline before considering wider rollout.

Connected evidence

Connect the whole picture.

Select an entity. Follow its evidence. See what a proposed change touches.

Interactive product illustration.
Fictional data; figures are examples.

Source inspector

Example evidence

SRC-03 / Spreadsheet

Handoff records

Handoff-records.csv · 60 records · September sample

60 fictional handoffs. 18 have no delivery owner at submission and are returned for clarification. Mean cycle time: 8.4 days. This sample supports investigation; it does not establish causation.

First 6 of 60 fictional records
ID	Client	Owner at submission	Days
NS-001	Alder & Co	Missing	11.2
NS-002	Fern Studio	Missing	11.2
NS-003	Harbour Works	Missing	11.2
NS-004	Juniper Group	Jordan Lee	7.2
NS-005	Cedar Partners	Sam Rivera	7.2
NS-006	Alder & Co	Alex Morgan	7.2

Authored fictional source for this product preview.

Download the complete demo source pack

Organization Brain is shown above. Enable JavaScript to explore the other views and inspect sources, or download the fictional source pack.

Think with your evidence.

Ask focused questions, investigate a handoff and compare possible changes. Studio brings project sources into the conversation and keeps the reasoning open to review.

Explore a guided example

Why do invoices return for clarification?

I’ll connect the source notes to the missing-owner rule.

Invoice fixturesWalkthrough notesInvoice SOP

One missing owner. A repeated handoff.

In the Northstar example, invoices without an owner return for clarification. Connect the SOP and walkthrough notes to the change you want to make.

Invoice routing logicRule → review queue

Queue classification only · approval stays with the team.

Missing owner takes precedence over amount.PS-SRC-02 · Invoice handling SOP

From understanding to action

Useful work, at every step.

Leave with something the next person can use. Keep the output connected to the sources, assumptions and decisions that shaped it.

Understand

Cited findings

Process maps, source registers and a shared view of the work.

Decide

Decision briefs

Scenarios, assumptions and the reasoning behind the selected direction.

Design

Working specifications

Target processes, SOPs, requirements and native workflow artifacts.

Deliver

Reviewed change

Plans, owners, version reviews and release decisions.

Connected context

The evidence gets more useful as the work moves forward.

A source can explain a process, support a finding and inform a design. Keep those relationships visible as the project develops, so the next decision can build on what the team already knows.

01 / The source
A walkthrough shows the handoff.
Start with something your team can inspect.
02 / The finding
Ownership is unclear at a critical step.
Connect the explanation to supporting evidence.
03 / The decision
Clarify the rule before automating.
Record the chosen response and its assumptions.
04 / The change
A reviewed process and delivery plan.
Carry that reasoning into design and approval.

Illustrative handoff example

Connected evidence, decisions and value

The journey has a memory. Follow the reasoning both ways.

Each source, finding, decision and design stays part of the same story. Explore how that continuity extends into a business case: inspect the evidence, challenge the assumptions and trace projected ROI back to its basis.

ProcessScout/Evidence to value

Fictional working example

NORTHSTAR SERVICES / CLIENT ONBOARDING

A better handoff. An explainable return.

01 / SOURCE REGISTER

Start with something
you can inspect.

Source evidence

Inspect a source

Handoff-records.csvFictional source

60handoffs in the sample

18missing a delivery owner

8.4 daysmean cycle time

First five records · September sample
Handoff	Delivery owner	Cycle time
NS-001	Not assigned	11.2 days
NS-002	Not assigned	11.2 days
NS-003	Not assigned	11.2 days
NS-004	Jordan Lee	7.2 days
NS-005	Sam Rivera	7.2 days

Source records support a finding. Financial estimates have their own documented basis.

Evidence. Assumptions. Decisions. Connected in both directions.Inspect the full example

Enable JavaScript to explore all five stages and change the model. The source records and baseline return are shown above. Download the evidence and assumptions.

From design to execution

A design you can inspect. A run you can examine.

See how one business rule becomes a native workflow, with conversion findings and recorded sandbox results.

Open the full case study

CASE FILE 01 / INVOICE ROUTINGSynthetic business data · Recorded local n8n run

THE SOURCE / SELECT AN INVOICE

NORTHSTAROFFICE SUPPLY

InvoiceINV-103

Amount · USD$1,250

Assigned owner: Not provided
Expected queue: Needs information

RECORDED RESULTNeeds information✓ Matches expected queue

Authored invoice fixture · PS-RULE-01

Read the source notes

THE DECISION / AN EXPLICIT RULE

Check the owner.
Then the amount.

A reminder cannot fix a missing owner. This example chooses a routing rule with a separate path for incomplete invoices.

PS-RULE-01 · AUTHORED LOGIC

if owner is blank
  needs_information

else if amount > 1,000
  manager_review

else
  standard_review

Routes for review. It does not approve or pay an invoice.

Inspect the decision Download generated workflow

THE RUN / OBSERVED BEHAVIOR

5/5

Queue checks passedRecorded sandbox execution

Select a case to inspect its input and result.

What this demonstrates

A real product compiler generated the native artifact from authored input. An isolated n8n run checked the five synthetic cases.

Inspect recorded results

Recorded using a proposed compiler fix. Human approval, external integrations and production release were not tested.

See the full evidence and limitations

Your first project

Start with one question worth answering.

You can build understanding progressively. A useful first project has a clear boundary, representative evidence and people who can challenge the answer.

An example starting brief

“What makes a new client wait between signing and the first delivery?”

The boundary

From signed agreement to a project ready to start.

The decision

Which handoff should we change first, and why?

Illustrative project · not a required template

01
Bring a few representative cases
Include a normal case, a delayed one and an exception. A document, tracker export and walkthrough can reveal different parts of the same process.
02
Identify the people who know the work
Include someone who performs it, someone who owns it and someone who can make the next decision. Capture the constraints they need respected.
03
Define what a better result would mean
Choose a measure such as elapsed time, rework or incomplete handoffs. Record its source and current baseline before treating a future estimate as a result.

A practical start

Before your first project.

Do we need every system connected?

Start with relevant documents, examples and walkthroughs. Evaluate connections where they add useful evidence, and confirm the supported operations and permissions before relying on them.

What can we produce?

Depending on the tools in your plan, the workspace supports cited analysis, process maps, scenario comparisons, target designs, documents and native workflow artifacts. The capabilities page explains the inputs, outputs and review responsibilities for each area.

Can we bring our existing advisor?

Discuss the project, participants and access roles during onboarding. The aim is a shared body of evidence that your internal team and advisor can work through together.

What needs to happen before a workflow runs?

Confirm target support, mappings, credentials and environment access. Review conversion findings, validate the artifact and approve the version intended for release. Publication and recovery support differ by provider.

AI and your data

AI sees the connections. You set the boundaries.

Use project context for analysis with configurable privacy controls. Review access, provider processing and retention before bringing client evidence into the workspace.

Read security, AI & data details

Set the audience.

Use organization, project and client-workspace roles to control access.

Choose the privacy level.

Balanced masking is the default for detected personal information in AI-bound text.

Keep training opt-in.

ProcessScout training datasets require explicit project training consent.

An optional next step

Take the plan into delivery.

Lead implementation with your team or your chosen partner. If you need ProcessScout to configure applications, connect workflows or manage an agreed service, scope that work after the discovery and design decisions.

Explore scoped implementation Discuss your delivery needs

ProcessScout Operating System is a delivery service for an agreed plan. It is not required to use the platform or buy an Edge assessment.

Start making progress

Put your next move in motion.

Open a workspace, investigate a bottleneck with Edge, or build the right enterprise scope with us.

01

LEAD THE WORK

Build your first project.

Give your team a shared place to capture evidence, investigate the business and prepare change.

Bring documents, recordings and team knowledge
Explore processes, scenarios and designs
Keep decisions and delivery connected

$499USD / month · Starter

Start your 14-day trial Try a tool freeChoose your plan and billing during signup.Compare software plans

02

GET A GUIDED ASSESSMENT

Find the right change.

Work with Sarah and a senior analyst to turn one troublesome workflow into a practical way forward.

Three evidence-backed opportunities
A reviewed Trail Map and 90-day plan
A starter asset and two outcome check-ins

$1,500USD · one assessment

Start your Edge assessmentReview your brief, scope and terms before paying.Explore what Edge delivers

03

ALIGN A LARGER ORGANIZATION

Scope your enterprise rollout.

Bring the workflow, teams and requirements. Agree a package and onboarding approach that fits.

Discuss access, security and procurement
Confirm connections and deployment needs
Agree support and onboarding scope

Let’s talkCustom enterprise pricing

Discuss enterprise requirementsSend your requirements. We’ll arrange the next step.Review security & data

Starter & Professional: 14-day trial. $1 card verification, credited to your first invoice. Your selected plan starts after the trial unless you cancel. Compare plans

Let’s find your next move

Your business has a next chapter.

Bring a process, a bottleneck or an ambition. Let’s explore what a more connected view could make possible.

Create your workspace Try a tool free Book a walkthrough

Understand the business. Move the work forward.

From understanding the work to making change happen.

The work tells the story.

Ready for delivery

Make the invisible visible.

Give the change a shape.

Work through what changes.

Customer CRM

Readiness check

Project workspace

From the design to the build.

The whole picture. In working detail.

Organization Brain

Studio

The delay starts before delivery accepts the work.

Start with the handoff, keep the systems you use.

Processes

Scenarios

Clarify the handoff

Automate the handoff

Connect client onboarding

Workflow design

Documents

A clearer handoff. A practical next step.

What the evidence says

The proposed change

How we will know

Every handoff has a person behind it.

Check readiness

Handle the exception

Accept and begin

From an agreed rule to a measured pilot.

Weeks 1–2 · agree the rules

Weeks 3–4 · build and test

Weeks 5–6 · pilot and review

Connect the whole picture.

Ask a better question.

Make the work visible.

Give every option a fair hearing.

Connect the design to execution.

Turn the thinking into useful work.

Think with your evidence.

One missing owner. A repeated handoff.

Choose the change for a reason.

Build from the rule. Test the output.

Useful work, at every step.

Cited findings

Decision briefs

Working specifications

Reviewed change

The evidence gets more useful as the work moves forward.

A walkthrough shows the handoff.

Ownership is unclear at a critical step.

Clarify the rule before automating.

A reviewed process and delivery plan.

The journey has a memory. Follow the reasoning both ways.

A better handoff. An explainable return.

Start with somethingyou can inspect.

The ownership checkhappens too late.

A clearer handoff.The same business systems.

See what thereturn depends on.

A number you canwork backwards from.

A design you can inspect. A run you can examine.

Check the owner.Then the amount.

Start with one question worth answering.

Bring a few representative cases

Identify the people who know the work

Define what a better result would mean

Before your first project.

AI sees the connections. You set the boundaries.

Set the audience.

Start with something
you can inspect.

The ownership check
happens too late.

A clearer handoff.
The same business systems.

See what the
return depends on.

A number you can
work backwards from.

Check the owner.
Then the amount.