Sample work / original examples
Look inside
the working method.
Inspect the instructions, checks and handoffs we would work through when scoping delivery. Every artifact below is illustrative, with fictional scenarios or synthetic data. These are examples to review, not client results.
See how an engagement is scopedA support playbook you can inspect.01 / Handling & handoff+
01 / Handling & handoff
A support playbook you can inspect.
An illustrative order-support queue: permitted work, decision limits, escalation fields and readiness checks.
Original fictional example. No client or live operation is represented.
Download example .md- 01Scope: order-status enquiries in one agreed queue
- 02Decision boundary: refund exceptions stay with the client
- 03Handoff: reason, evidence, owner and next update
A score with evidence behind it.02 / Quality & coaching+
02 / Quality & coaching
A score with evidence behind it.
A worked fictional interaction, a five-part scorecard and coaching that follows from what the agent actually said.
The score is illustrative. It is not a Culvion performance result or a universal target.
Download example .md- 01Maximum score: 100 points
- 02Worked score: 24 + 20 + 18 + 12 + 10 = 84
- 03The next step: agree an update time and improve the case note
A report that adds up.03 / Reporting & action+
03 / Reporting & action
A report that adds up.
Synthetic intake, completed work and backlog, with an explicit reconciliation and a short decision log.
Every figure is synthetic. This is a reporting example, not a customer case study.
Download example .md- 0150 opening + 800 received − 760 resolved = 90 closing
- 02Voice: 30 closing · Email: 30 · Chat: 30
- 03Quality example: 2,520 earned / 3,000 possible = 84%
A proposal starts with a boundary.04 / Software scope+
04 / Software scope
A proposal starts with a boundary.
A sample request-portal scope with users, exclusions, acceptance checks, dependencies and handover questions.
An illustrative scope document. It is not a quote, binding agreement or completed build.
Download example .md- 01First release: submit, review and view request status
- 02Out of scope: payments, native apps and automated decisions
- 03To agree: effort, price, schedule, ownership and support
See the work connect
The customer asks.
What happens next?
Try an order enquiry, an access request or a new business lead. Follow the context from the customer to the person who owns the next step.
Try the connected workflowOrder record + handling rule
↓Make it about your work
A blank page,
with better prompts.
A useful next step
Your work will have its own details.
A rough brief is enough. There is no minimum engagement size; scope, cost and availability are agreed before work starts.