Book a fit call

Workflows Directory

Find your team’s next superpower.

Results

204 workflow templates, showing 49 to 72

  • Current experience baseline

    Before a redesign, the design lead gets a baseline built from the captures and page list they supply: each page read with its content and design observations, the patterns that recur, and the pages outside the evidence. The lead confirms the baseline and sets the scope.

    Starts it
    Design lead
    Brings
    export, notes, document
    Gets
    6 outputs

  • Customer case study

    With a customer who has agreed to help, prepare the interview, then turn their words and the figures they supply into a case study in a short and a long version. Every quotation and number is listed for the customer to approve in writing, and nothing is published or named before they do.

    Starts it
    Marketer
    Brings
    export, notes, document, pasted text
    Gets
    5 outputs

  • Customer feedback themes

    Each month your support lead sees what customers keep telling you: tickets, disputes, reviews and survey comments grouped into themes with counts and quotations, the three issues most worth fixing with a proposed fix and owner, and a note for customers once a fix ships. A person decides every fix.

    Starts it
    Support lead
    Brings
    export, notes, document
    Gets
    5 outputs

  • Customer interview synthesis

    Turn a stack of customer call notes into the answer to one question, in your customers’ own words. Every quotation is cited to the note it came from, every theme shows its confidence and the evidence against it, and nothing is claimed that the notes do not say.

    Starts it
    Founder
    Brings
    notes
    Gets
    5 outputs

  • Customer onboarding plan

    For every new customer, your customer success lead gets one plan for the first weeks: the result the customer must reach, the fewest milestones that get them there with an owner on each side, the promises both sides made, and each message as a draft. Nothing is sent until a person approves it.

    Starts it
    Customer success lead
    Brings
    notes, document
    Gets
    6 outputs

  • Customer reply drafting

    Every customer gets the reply your best person would write. Hand over the customer's message, your tone guide and your approved answers, and get back a draft in your voice where every statement and every promise traces to something you approved. A person on your team reads it, edits it and sends it.

    Starts it
    Support agent
    Brings
    notes, document, pasted text
    Gets
    3 outputs

  • Customer satisfaction detractor follow-up

    Every week your support lead gets each low satisfaction or recommendation score with the ticket behind it: the customer's own words, what went wrong as far as the ticket shows, a suggested owner and a draft message, plus the trend and a warning wherever the numbers are too thin to read. A person sends every message.

    Starts it
    Support lead
    Brings
    export, notes, pasted text
    Gets
    7 outputs

  • Dashboard brief

    Before anyone builds the dashboard, the requester gets one brief that settles the work: the decisions it serves, what is shown, each metric's definition, the filters, notes on every source and who refreshes it. The requester approves what is shown and the definitions.

    Starts it
    Analyst
    Brings
    export, notes
    Gets
    4 outputs

  • Dataset profile

    Before anyone joins or relies on a new export, the analyst gets one profile of it: what one row stands for, where keys repeat, what is missing, which values look odd, and a numbered list of questions for the data owner. No data is changed and no verdict is given.

    Starts it
    Analyst
    Brings
    export, notes
    Gets
    4 outputs

  • Deal close plan

    Your account executive holds one late-stage deal on two pages: the buyer's case for buying now, counted from the buyer's own figures, and a dated plan of every step to signature with its owner on each side. The seller decides what the buyer sees; nothing reaches the sales system without approval.

    Starts it
    Account executive
    Brings
    export, notes, document
    Gets
    4 outputs

  • Decision log

    Your chief of staff keeps one register of what the leadership actually approved, across every meeting and message: each decision with who approved it, each action with one owner and a date, what is overdue, and a flag wherever a new decision clashes with an earlier one or revives a rejected idea.

    Starts it
    Chief of staff
    Brings
    export, notes, pasted text
    Gets
    5 outputs

  • Delegation brief and follow-up

    Every task a manager hands over goes with a clear brief: what to deliver, in what form, by what date and time, why it matters, who will use it, what the person may decide alone and when the manager will check in. Each week, one list shows what is open, what is late and the next note to send.

    Starts it
    Manager
    Brings
    export, notes, document, pasted text
    Gets
    5 outputs

  • Departing-employee knowledge capture

    When someone is leaving or changing role, their manager gets an interview guide aimed at what only that person knows, then a handover document the successor can work from, every point traced to the conversations and marked with how sure it is. Nothing is shared until the manager approves.

    Starts it
    Manager
    Brings
    export, notes, pasted text
    Gets
    2 outputs

  • Design assumption change register

    When client criteria or design assumptions change, the project engineer gets one sourced register: what changed, which recorded requirements it touches, how firm each source is, and what still needs confirmation. No design basis is altered.

    Starts it
    Project engineer
    Brings
    export, notes
    Gets
    6 outputs

  • Design handoff record

    Before engineering starts, the design owner gets one record built from the approved design: every state, token, breakpoint and content rule either covered or flagged, with each unstated behaviour written as a question. The engineer confirms the questions are resolved.

    Starts it
    Design owner
    Brings
    export, notes
    Gets
    6 outputs

  • Discount request review

    Before a price below list goes to a customer, whoever approves it gets one page: the discount and what it costs in margin, every clause of your own written policy met or missed, who approves and in what order, and what the customer gives in return. A person decides; nothing is sent.

    Starts it
    Sales lead
    Brings
    export, notes, document
    Gets
    7 outputs
    • Sales
    • Logistics and trade (filtered by)
    • Software technology (filtered by)

  • Donor thank-you drafts

    Donor services staff get one draft thank-you for each new gift, written from the confirmed gift details, the donor's communication preferences and the organization's approved program language. A person checks and sends every message; nothing asks for another gift.

    Starts it
    Donor services staff member
    Brings
    export, notes, document
    Gets
    3 outputs

  • Email sequence drafting

    People who asked to hear from you get emails worth opening: a welcome, a nurture sequence or a new customer's onboarding, drafted in your voice, each email with one job and one ask, every claim traced to your own facts, and a clear end. You read, load and send them yourself.

    Starts it
    Marketer
    Brings
    notes, document
    Gets
    4 outputs

  • Emergency drill brief

    Before a fire, evacuation or other drill, the site or office manager gets one brief: the scenario the responsible person has approved, who does what, what each observer records, and the questions for the debrief. It writes no emergency plan.

    Starts it
    Site manager
    Brings
    export, notes
    Gets
    4 outputs

  • Emissions activity data schedule

    When the reporting period closes, the environmental reporting owner gets one source-linked schedule of energy, fuel and transport quantities with units and the boundary supplied, estimates kept apart from measured activity, missing factor references and gaps listed. It calculates no emissions figure.

    Starts it
    Environmental reporting owner
    Brings
    export, notes
    Gets
    5 outputs

  • Employee offboarding and handover checklist

    When someone leaves, your HR lead and their manager share one checklist: every piece of their work handed to a named colleague before the last day, every system on your access register removed by its owner at a set time, and every item of equipment back. Nothing is removed or sent without a person.

    Starts it
    People lead
    Brings
    export, notes
    Gets
    7 outputs

  • Employee onboarding plan

    Every new colleague starts with a first week and a first 90 days planned to the standard of your best manager: what to read, who to meet, what to practice and what productive means at day 30, 60 and 90.

    Starts it
    Hiring manager
    Brings
    notes, document
    Gets
    6 outputs

  • Engineering change affected records index

    When an engineering change request enters review, the document controller gets one index: the assemblies, revisions, stock and open purchase orders the change reaches in the exports supplied, and a question for each owner wherever the records are unclear.

    Starts it
    Document controller
    Brings
    export, notes
    Gets
    3 outputs

  • Ergonomic review inputs

    For a supervisor preparing for an ergonomics assessor or a worker's complaint about a task: a task observation record of each step's movements, durations, loads and measurements as supplied, the measurements still missing, and what the people who do the task said.

    Starts it
    Supervisor
    Brings
    export, notes
    Gets
    4 outputs