Every finding in a Wolfix report falls into one of two camps: a gap that stops you from operating, or a gap that simply improves how you operate. Wolfix calls the first kind a blocker and the second a guide. Telling them apart is the single most useful skill for reading a report — it decides what you do today and what can wait.
The dividing line
The question Wolfix asks of every finding is simple: if you ignore this, can you still legally and reliably charge a customer?
- If the answer is no, it is a blocker. A blocker creates legal liability or breaks your ability to take money — a missing privacy policy, absent terms of service, or a payment processor that is not configured.
- If the answer is yes, it is a guide. A guide is a real improvement, but skipping it does not put you at immediate risk — a missing OG image, a vague tagline, or an empty App Store description.
Between those two extremes sit risks — findings that will not stop you launching today but will catch up with you in weeks or months. Wolfix surfaces risks alongside blockers and guides so nothing important hides in the middle.
Blockers
Fix before you charge anyone. These create legal exposure or break payments outright. Wolfix sorts them to the top of every report.
Risks
Fix at or shortly after launch. No immediate liability, but real operational, security, or compliance exposure over time.
Guides
Recommended polish. They raise quality and trust but carry no immediate risk. Safe to schedule after you are live.
Notes
Awareness only. Wolfix surfaces them because some operators want to know — no action is required unless you choose to act.
Why the split exists
Wolfix is built to take you from a working app to a legitimate operating business. The blocker-versus-guide split mirrors that goal: it separates the work that unlocks charging customers from the work that strengthens the business once money is flowing.
This matters because a long list of findings can feel paralysing. Sorting by blockers turns it into a short, finite checklist — usually a handful of items — that stands between you and your first paid customer. Everything else is genuine, but it is not in the way.
Work top to bottom
Reports are pre-sorted: blockers first, then risks, then guides. If you only have an hour, spend it on blockers. Each one you clear removes a hard barrier to operating.
How blockers show up in the report
Blockers are counted in the Blockers stat tile at the top of the report and pinned to the top of the findings list. The number in that tile is the count you most want to drive to zero before launch.
Each blocker card explains the gap, why it blocks you, and what Wolfix can do about it — generate the missing document, hand you a code-fix prompt, or connect you to a vetted partner. Guides use the same card layout but sit lower in the list and are not counted as blockers.
A guide can become a blocker
Severity is contextual. Cookie consent is a guide for a static brochure site but a blocker for an app serving EU users with tracking scripts. Wolfix decides per finding using what it detected during the scan — see severity and scoring.
What to do with each
| Finding type | When to act | Typical action | | --- | --- | --- | | Blocker | Before charging a customer | Generate the document, paste the code fix, or use a referral | | Risk | At launch or soon after | Schedule it into your launch checklist | | Guide | Once you are live | Batch them into a polish pass | | Note | Optional | Read for awareness, act only if it matters to you |
Re-run a scan after you clear blockers to confirm the count has dropped. Wolfix stores each report separately, so you can see the before and after.