When you hire an agency, the scope lives in a statement of work that nobody reads after the kickoff call. When a question comes up in month three, such as "is fixing the pricing page in scope?", you end up in an email thread. We wanted the scope for every job the crews do to be public, specific and short. That is what the how-to library is.
This post explains how the library is organised and how to use it, whether you are evaluating Spryxa, planning a quarter, or deciding what to approve.
One job, one guide
Each guide covers one job to be done, phrased the way you would say it: recover stalled leads, fix a slow landing page, close a search gap, check new copy against your brand voice. Guides are grouped by the crew that owns the job, so you can browse by function the same way you would think about an org chart.
Some jobs need more than one crew. A search gap, for example, is owned by the Search Crew but usually hands a page brief to the Content Crew and a site fix to the Website Crew. Where that happens, the guide names the supporting crews, so you know who else touches the work.
What every guide contains
Every guide follows the same structure. Once you have read one, you can scan the rest in a minute each.
- The one-line answer. What the crew does for this job, in a sentence.
- When to use it. The situation that makes the job worth doing. If that situation does not describe you, skip the guide.
- The steps, in order. Four to seven steps, each marked as done by the crew or by you. At least one step is always yours: the approval or the decision.
- What you approve. The specific thing that waits for a person in this job.
- What to connect. The integrations the job needs, such as Google Search Console, Google Analytics 4 or an ad account.
- How it is measured. The signal that tells you whether it worked.
- Limits. What the crew will not do here, or what it needs from you first.
- Status. Live, or planned if the app does not yet do the job end to end.
The last two fields are the ones we would ask you to read most carefully. A vendor page that only lists what a product does is half a page. The limits and the status are where you find out whether it fits your situation.
Why the guides are written the way they are
The guides follow a few rules we hold ourselves to:
- They only claim what the crew's contract supports. Each crew has a written output contract, human gate and list of limitations in the product. The guides quote those. If the app has not shipped something, the guide says planned.
- No invented numbers. No made-up lift figures, customer names or benchmark claims. The only numbers are facts of the product, such as the audit's 23 analysis types.
- You are always in the loop. Every guide includes at least one step that belongs to you.
These rules make the guides less exciting than a typical landing page. They also make them something you can forward to your CFO or your head of sales without a caveat.
Three ways to use the library
1. To evaluate whether Spryxa fits
Start with the jobs your current agency or contractor does for you. Find the matching guide and compare. Look at the approval step: is that where you want the control to sit? Look at the connectors: do you use those tools? Look at the limits: is there a gap you would still need someone else to cover? You will know within half an hour whether the crew covers enough of your SOW to matter.
2. To scope a quarter
Take your quarterly goals and map each one to a job in the library. "More qualified demos from organic search" maps to the Search Crew's guides and, downstream, to the Website Crew's conversion guides. You get a list of jobs, the crews that own them, and the connections you need to set up before the quarter starts. That last part alone saves a few weeks, because most marketing plans stall on access, not ideas.
3. To know what you are approving
When something lands in your approval queue, the guide for that job tells you what the crew did before it got to you and what happens after you approve. That makes review faster. You are checking the thing that needs a human judgement, such as the claim, the audience, the budget or the destination, not re-doing the crew's work.
What the approval gates look like across crews
As a quick reference, these are the kinds of actions that wait for you, in the product's own terms:
- Website Crew: visual or risky changes are staged for review. Low-risk fixes may ship inside guardrails.
- Content Crew: a person reviews the draft, the claims and the publishing destination.
- Paid Media Crew: budget, targeting, creative and campaign launches need explicit approval.
- Outreach Crew: a person reviews recipients, consent and every message before send.
- Pipeline Crew: people approve lead ownership, CRM updates and any outbound follow-up.
- Measurement Crew: it reports, and people decide what to change. It does not execute changes.
If a type of work has earned your trust, you can put it on autopilot. Until you do, it waits.
Where to start
If you are new, do not read the library front to back. Run the free audit first. It maps each finding to the crew that fixes it, and from there the relevant guide tells you exactly what happens next. The library is the reference. The audit tells you which page of it matters for your site.
Find out which guides apply to your site. Browse the how-to library, or let the audit tell you where to look. Run your free Spryxa audit.