Positioning
Decision
Section titled “Decision”Position the specific service, not Workflow Control by itself. Start from the alternatives a buyer would use if FZF did not exist, then connect FZF’s unique operating attributes to value for the best-fit staffing customer.
Use buyer language such as staffing billing control, invoice exception automation, or workers’ compensation follow-up. Do not ask the market to learn “Workflow Control” as a new category. It is the shared mechanism behind the service.
The positioning sequence
Section titled “The positioning sequence”Apply April Dunford’s sequence in this order. Do not jump to a tagline before the choices are explicit.
| Step | Decision | Required output |
|---|---|---|
| 1 | Competitive alternatives | What would a strong-fit buyer do instead, including doing nothing? |
| 2 | Unique attributes | What can FZF credibly do that the relevant alternatives do not? |
| 3 | Value | What operational and business change follows from those attributes? |
| 4 | Best-fit customer | Which staffing firms, workflows, buyers, and triggers make the difference matter now? |
| 5 | Market context | Which existing buyer language makes the value obvious without category education? |
| 6 | Message check | Does the resulting message pass the 4 U’s without exceeding current evidence? |
1. Start with real alternatives
Section titled “1. Start with real alternatives”The competitor is often the current operating model, not another specialist firm.
| Alternative | When it is rational | FZF’s relevant difference |
|---|---|---|
| Spreadsheets, inboxes, and current staff | Volume and consequence are low, and experienced staff can reconstruct status | FZF makes state, rules, owners, deadlines, evidence, and recovery explicit across the workflow |
| Hire another coordinator | The need is genuinely more queue capacity | FZF targets repeated coordination and exception causes; it does not sell another person to clear the queue |
| Extend or replace the ATS, VMS, payroll, claims, or accounting system | One platform can own the full workflow and migration is justified | FZF keeps systems of record and controls the client-specific path between them |
| Internal IT or an integration platform | The client has staffing workflow expertise, delivery capacity, and long-term operating ownership | FZF combines workflow diagnosis, implementation, and retained control accountability |
| Development or integration consultancy | The buyer needs project capacity and will own the result after handoff | FZF packages a paid design decision, fixed-price Build, and recurring Run path around one operating outcome |
| BPO, funding, factoring, or collections provider | The buyer wants to outsource transactions or finance working capital | FZF improves the client’s control while the client retains staff, capital, relationships, and decisions |
If the buyer wants the rational alternative more than the FZF difference, qualify out. Do not manufacture differentiation.
2. Connect attributes to value
Section titled “2. Connect attributes to value”FZF’s strongest cross-service attributes are:
| Unique attribute | Operational effect | Buyer value to test |
|---|---|---|
| No migration required | The existing stack remains authoritative | Lower implementation disruption and less replacement risk |
| Client-specific rules, not one template | End-client evidence, timing, approval, and exception differences become explicit | Less dependence on inbox knowledge and fewer preventable failures |
| Healthy work continues while exceptions stop | A small bad subset does not block the whole run | More consistent throughput and focused review |
| Human authority is designed into the path | Unsafe or consequential decisions stay with authorized people | Automation without silent financial, medical, legal, or employment decisions |
| Fixed-price implementation | Scope, acceptance, and implementation risk are explicit | A fundable decision instead of open-ended development hours |
| Recurring control with a shrinking-work loop | Repeated exception classes enter the automation backlog | The control adapts while avoidable manual coordination can decline |
Only the first four are delivery attributes. The last two are commercial-model attributes; their canonical terms are in the Offer ladder.
3. Define best fit
Section titled “3. Define best fit”Best-fit accounts usually have:
- A US contingent staffing operation with multiple clients, branches, systems, portals, or rule sets.
- A high-consequence workflow that crosses system and organizational boundaries.
- Manual residue after a platform implementation, often visible in spreadsheets, inboxes, and side processes.
- A named operating owner and an economic or risk consequence that leadership recognizes.
- Representative records and willingness to establish a baseline.
- A requirement to keep existing systems and human decision authority in place.
The sharpest trigger remains a firm 3–12 months after a major platform go-live with unresolved manual residue. Treat that timing as a targeting hypothesis and validate it through the Sales playbook, not as a universal fact.
4. Choose market context
Section titled “4. Choose market context”Use the category the buyer already understands:
| Service | Useful context | Do not lead with |
|---|---|---|
| Staffing Billing Control | Staffing billing operations, invoice delivery, invoice exception control, timesheet-to-cash | Generic workflow platform, AI automation, accounts-receivable outsourcing |
| Staffing Workers’ Compensation Control | Staffing workers’ compensation operations, injury follow-up, claim evidence and deadline control | Claims adjudication, medical management, legal advice, generic risk dashboard |
| Candidates | The buyer’s current workflow wording during research | A new service name before promotion gates pass |
5. Check the message with the 4 U’s
Section titled “5. Check the message with the 4 U’s”The 4 U’s are a message-quality check, not the portfolio scoring model.
| U | Test | Failure signal |
|---|---|---|
| Useful | Is the consequence important enough to fund? | The message promises visibility or convenience without economic, capacity, or risk value |
| Urgent | Why act in this cycle? | No live deadline, recurring loss, change event, or compounding exposure exists |
| Unique | Why FZF rather than the actual alternative? | The message could describe any dashboard, integrator, software product, or BPO |
| Ultra-specific | Are buyer, workflow, outcome, and measure obvious? | The message uses “operations,” “automation,” or “AI” without a bounded job |
Score each from 1 to 5 for copy comparison, but do not combine that score with Portfolio prioritization. A message should not ship if any U is below 3 or if its wording exceeds the claim register.
Positioning template
Section titled “Positioning template”For [best-fit staffing customer and buyer] who need to [high-consequence job], [specific service] is a [familiar market context] that [value stated at an allowed evidence level]. Unlike [primary alternatives], FZF [unique attributes] while [systems and consequential decisions that remain with the client].
Use the template as a decision check, not mandatory public syntax. Shorten the final message only after every field is supported.
Guardrails
Section titled “Guardrails”- Do not call FZF SaaS, BPO, staff augmentation, a factoring company, a collections provider, or a payroll funder.
- Do not claim a product category or imply that Workflow Control replaces a system of record.
- Do not claim that all products structurally fail; identify the specific cross-system or client-rule gap in this account.
- Do not convert intended value into achieved value. Match every result statement to Validation and evidence.
- Do not use “AI” as the differentiator. The differentiator is accountable workflow control with safe human gates.
- Do not attack an active platform migration. Re-enter where the platform’s defined scope leaves operational residue.