Process

Diagnosis before prescription.

Most agencies sell a deliverable on the first call. Strygon sells a diagnosis, and the deliverable follows from it.

Start a buildSee the work
01Leaves: a system map
Map01
Phase 01 of 5

$ strygon map --env=production

Every tool in use, inventoried

Every handoff between them

Who owns each step

Map

Every system, every handoff, every place data changes hands.

02Leaves: a written read
Diagnose02
Phase 02 of 5

$ strygon audit --trace revenue

Where the path breaks

What is still done by hand

Which numbers disagree

Diagnose

Where leads leak, where work is manual, where numbers disagree.

03Leaves: scope, sequence, cost
Architect03
Phase 03 of 5

$ strygon plan --output scope.md

Scope, in writing

Build order and dependencies

Cost before work starts

Architect

A written plan with scope, sequence, and cost before anything gets built. The plan is a document the client keeps.

04Leaves: a working system
Build04
Phase 04 of 5

$ strygon build --watch

Built against the plan

Tested on the deployed build

Handover documented

Build

A dedicated delivery team builds against that plan. Nothing gets made that wasn’t drawn first.

05Leaves: a monthly readout
Operate05
Phase 05 of 5

$ strygon status --since 30d

Monitored while it runs

Changed as the business changes

Reported once a month

Operate

Monitoring, iteration, and a monthly number that means something.

Engagement sequence · always in this orderEach phase leaves an artifact the client keeps

The artifact

The plan exists before anyone touches a tool: scope, sequence, and cost, written down. It is the one part of the engagement that outlives the engagement, and it leaves with the client either way.

Start

Start with what’s broken.

Send the situation in a paragraph. Strygon comes back with a read on what’s likely wrong and what it would take to fix, before anyone talks about price.

Most builds start withleads dying in an inbox., three half-finished pipelines., follow-up nobody owns., numbers that never agree., four vendors blaming each other.

Or email hello@strygon.com

What to send
A paragraph. What broke, and where it shows up.
What comes back
A read on what is likely wrong and what fixing it takes.
Price
The last conversation, not the first