Missions
A Mission is a responsibility, not a workflow.
You give Ziggyy an outcome your business needs again and again. Ziggyy works out what it takes — the systems, the rules, where people step in, what counts as done — and keeps carrying it.
What a Mission is
Everything needed to carry the work responsibly.
A Mission is a defined, recurring business outcome Ziggyy is responsible for operating. You describe it in a sentence; Ziggyy shapes the rest with you.
Give Ziggyy the outcome. Ziggyy figures out the work.
- ObjectiveWhat outcome are we trying to achieve?
- Every Amazon order over $500 is in the Orders sheet — once, and current.
- ContextWhat does Ziggyy need to know about the business?
- Northwind sells online and on Amazon. Operations owns orders.
- TriggerWhen should the Mission run?
- Whenever a new order arrives.
- RulesWhat business logic matters?
- Only orders over $500. One row per order ID.
- SystemsWhich systems does it touch — with what access?
- Reads orders in Amazon Seller Central. Adds and updates rows in one Google Sheet. Nothing else.
- ControlsWhat happens automatically, and what needs a person?
- Rows are added automatically. Overwriting a conflicting row asks first. Refunds never happen.
- CompletionWhat evidence proves it succeeded?
- Every qualifying order appears exactly once and matches its current state.
- ExceptionsWhat happens when work can't finish?
- Orders with missing fields go to Operations. If the sheet can't be written, orders queue — none skipped.
Good Missions
Where a Mission earns its keep.
A strong Mission
- Happens repeatedly — hourly, weekly, or whenever something arrives
- Crosses systems, people or time
- Has a real finish line, not just a response
- Depends on rules, and has exceptions
- Sometimes needs a person to approve
- Needs proof that it actually got done
Probably not a Mission
- One app already does the whole job, start to finish
- A one-off question with no ongoing state
- “Automate everything in the company”
- Moving money without anyone's approval
Ziggyy will tell you when a single platform already does the job well.
Mission Maps
Every Mission has its own shape.
No shared template with the nouns swapped. Ziggyy draws each Mission's lifecycle from what it has to achieve — so you can see where systems take part, where your team steps in and what “done” means.
Research, qualify and record target accounts
Every week · Owner: Sales
01Discover
Companies that may fit
- Find companies that may fit
Systems: Public web
02Research
Decision-makers and evidence
- Identify the right decision-makers and the evidence
03Qualify
Checked against your ICP
- Check each against your ICP
- Contacts Ziggyy isn't sure about go to Sales
04Record
Prospects in HubSpot
- Add qualified prospects to HubSpot
Systems: HubSpot
05Prepare
Outreach ready for Sales approval
- Draft outreach for each prospect
Systems: Gmail
- Every outreach draft is approved by Sales before it's sent
06Verify
Verified next action for each prospect
- 25 qualified prospects recorded in HubSpot, each with its evidence
- Each has outreach ready for Sales
When work can't finish
Nothing is dropped. Unfinished work stays open until it's resolved.
Company doesn't match your ICP
- Recorded as not a fit, with the reason
- Not added to HubSpot
Decision-maker can't be confirmed
- Held for review with the evidence found
- Nothing drafted until it's confirmed
Company already in HubSpot
- The existing record is enriched, never duplicated
Not enough public evidence
- Kept as a candidate, not recorded
- Retried next run
Give every customer enquiry an owned next action
Whenever an enquiry arrives · Owner: Support
01Receive
Enquiry arrives
- Pick up each new enquiry
Systems: Zendesk
02Understand
Customer and account identified
- Identify the customer and their account
Systems: HubSpot
03Decide
Intent classified, next action chosen
- Classify the intent and choose the next action
- Refunds, chargebacks, legal threats and wholesale accounts go to Support
04Respond or route
Reply drafted or handed to a person
- Draft a reply, or route it to the right person
05Track
Owned next action within 30 minutes
- Track it until the next action is owned
- Every enquiry has an owned next action within 30 minutes
- Sensitive enquiries are with a person
- Anything without a next action within 30 minutes is escalated to Support
When work can't finish
Nothing is dropped. Unfinished work stays open until it's resolved.
Intent unclear
- Routed to Support with Ziggyy's best reading
- Kept open until someone owns it
No next action within 30 minutes
- Escalated to Support
- Stays open, never dropped
Customer not found
- Handled as a new contact
- Nothing assumed about their account
Zendesk can't be reached
- Enquiries queued, none skipped
- Retried until they're picked up
Watch traffic and conversion, and follow incidents to resolution
Every hour · Owner: Operations
01Observe
Website traffic and conversion read hourly
- Read website traffic and conversion hourly
Systems: GA4
02Compare
Against the normal range
- Compare with the normal range
03Detect
Material change classified
- Decide whether the change is material
04Escalate
Operations alerted
- Alert Operations in Slack
Systems: Slack
- Operations owns every incident until it's resolved
05Resolve
Resolved or handed off
- Follow the incident until it's resolved in Linear
- Each incident is resolved or explicitly handed off
- Every run is checked, including runs with a missing source
Systems: Linear
When work can't finish
Nothing is dropped. Unfinished work stays open until it's resolved.
A data source can't be read
- Reported as a gap, never as all clear
- Retried next run
Signals disagree
- Flagged to Operations with both readings
Incident has no owner
- Escalated along the escalation path
- Kept open until someone takes it
Alert couldn't be delivered
- Retried, then sent another way
- Kept open until acknowledged
Track qualifying Amazon orders in Google Sheets
Whenever a new order arrives · Owner: Operations
01Receive
New order in Amazon Seller Central
- Read each new order
Systems: Amazon Seller Central
02Filter
Orders over $500 selected
- Keep orders over $500
03Normalise
Fields mapped to the destination
- Map and normalise the fields
- Orders with missing or ambiguous fields go to Operations
04Deduplicate
Checked against what's already there
- Check the order ID against existing rows
05Write
Added or updated
- Add or update the row
Systems: Google Sheets
06Verify
Destination matches the source
- Every qualifying order appears exactly once
- Each row matches its order's current state
When work can't finish
Nothing is dropped. Unfinished work stays open until it's resolved.
An order is missing a required field
- Held back, never written half-filled
- Listed for Operations
Order already in the destination
- The existing row is updated, not duplicated
Fields no longer match the expected mapping
- Writing paused for affected fields
- You're asked to confirm the mapping
The destination can't be written
- Orders queued, none skipped
- Kept open until the row exists
Reconcile supplier invoices against purchase orders
Every week · Owner: Finance
01Receive
Supplier invoice received
- Detect new supplier invoices
- From email · Gmail
Systems: Gmail
02Match
Invoice and purchase order
- Read each invoice and its supporting files in Google Drive
- Find the matching purchase order in NetSuite
Systems: NetSuiteGoogle Drive
03Evaluate
Match, mismatch or above $1,000
- Compare supplier, PO number and amount
- Apply the $1,000 review threshold
- Invoices above $1,000 go to Finance for review
- Mismatches go to Finance to resolve
04Record & route
Result recorded, exceptions routed
- Record the result in NetSuite
- Route mismatches to Finance
- Send invoices above $1,000 to Finance
Systems: NetSuite
- Reconciliations above $25,000 need CFO sign-off before Ziggyy records them
05Verify
Verified reconciliation
- Every invoice received this week ends matched, in review, or open with a reason
- Each recorded result is confirmed in NetSuite
When work can't finish
Nothing is dropped. Unfinished work stays open until it's resolved.
No matching purchase order
- Kept open — never marked reconciled
- Missing purchase order requested from Finance
- Reconciliation resumes when it arrives
Invoice and purchase order disagree
- Differences recorded with the evidence
- Finance resolves the discrepancy
- Re-checked, then completed
NetSuite can't be reached
- Nothing is marked complete
- Retried on the next run
- You're told if it keeps failing
Mission vs. automation
Automation performs steps. Ziggyy owns the thread.
Automation tools are excellent when you know the exact trigger and steps. A Mission starts from the outcome — and keeps going after the first step fires.
Fast and reliable — when the happy path is the whole job.
When X happens, Ziggyy:
- Understands what happened
- Checks the relevant context
- Works out what state the work is in
- Applies your rules
- Takes the actions it's allowed to
- Asks for approval when required
- Checks the outcome actually happened
- Handles exceptions
- Recovers when it can
- Escalates when it should
- Records the evidence
- Continues until the outcome is complete
Already using Zapier, Make or n8n? Keep them for the steps they're good at. Missions are for the responsibility around them.
When things change
When the work changes, the Mission changes with it.
Tell Ziggyy in plain language. It shows exactly what changes — in the definition, the systems and the controls — before anything takes effect.
New access is never added silently, and rules you set are never relaxed without you.
“Send failed-order alerts to #fulfilment instead of #operations, and ask before updating any order over $5,000.”
- Alerts move to #fulfilment
- New rule: approval for orders over $5,000
- Access unchanged — nothing new requested
Completion
A Mission is done when the outcome is verified.
Not when an action ran. Each Mission defines what must be true, and Ziggyy checks that business state before calling anything complete.
Revenue
Research, qualify and record target accounts
Complete when
- 25 qualified prospects recorded in HubSpot, each with its evidence
- Each has outreach ready for Sales
Operations
Watch traffic and conversion, and follow incidents to resolution
Complete when
- Each incident is resolved or explicitly handed off
- Every run is checked, including runs with a missing source
Reconciliation
Reconcile supplier invoices against purchase orders
Complete when
- Every invoice received this week ends matched, in review, or open with a reason
- Each recorded result is confirmed in NetSuite
Know the pain, not the Mission?
That's normal. Start with what your team keeps chasing and Ziggyy helps turn it into a Mission.
What should Ziggyy carry for you?
Start with one outcome. Build from there.