Book a fit call

Workflows Directory

Find your team’s next superpower.

Results

218 workflow templates, showing 73 to 96

  • 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

  • Demand and supply review

    The operations lead gets one monthly review from the demand plan, confirmed supply and stock: where confirmed and likely demand outrun supply, what that does to inventory, and the decision each function head has to make. Sales ambition stays separate and nothing is forecast beyond your figures.

    Starts it
    Operations lead
    Brings
    export, notes
    Gets
    7 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

  • 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

  • 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

  • Event plan

    Whoever owns one event, a talk, a dinner, a webinar or a stand, gets one plan: the goal and target, who should be in the room, every step before, on and after the day with a date and an owner, and how each conversation is followed up. Nothing is booked, paid or sent by the assistant.

    Starts it
    Owner
    Brings
    export, notes, document
    Gets
    6 outputs

  • Executive situation brief

    Before a conversation that matters, with a key partner, a major customer or a co-founder, the executive gets one brief from the records they approve: the short version in a sentence, what is already decided and promised, what each side has said, the question to settle and the choices open. The executive decides.

    Starts it
    Executive
    Brings
    export, notes, document
    Gets
    9 outputs

  • Executive week-ahead calendar review

    Before the week starts, the executive assistant hands the executive one brief: every clash, every journey or run of meetings with too little time, every meeting with no stated purpose or no preparation time, and proposed time for the week's priorities. Nothing is accepted, declined, moved or sent.

    Starts it
    Executive assistant
    Brings
    export, notes
    Gets
    7 outputs

  • Expansion whitespace review

    For one account or a whole book, the account manager sees what each customer holds against what it could also use, the evidence for every gap, the plays ranked, and one next step and owner for each. A person decides what to propose; nothing goes into the sales system without approval.

    Starts it
    Account manager
    Brings
    export, notes
    Gets
    5 outputs

  • Feedback follow-through updates

    When a change ships or a decision lands on something customers asked for, your account owner gets the list of who asked, the confirmed status of each request, and an individual draft update for each person in the channel they prefer. No update promises a date or feature the team has not confirmed.

    Starts it
    Account manager
    Brings
    export, notes, document
    Gets
    5 outputs

  • Freight shortage record packet

    When a receiver reports missing or damaged freight, the claims coordinator gets one packet lining up dispatch quantities, warehouse scans, bill of lading, proof of delivery, photos and the customer report, with each unanswered question listed. It assigns no fault and sends nothing.

    Starts it
    Claims coordinator
    Brings
    export, notes
    Gets
    6 outputs

  • Funder report draft

    Before a funder report is due, the grants manager gets a draft written to the funder's own questions, with every number tied to a record, an index of the evidence behind each statement and a list of what is still unanswered. People verify it, approve it and submit it.

    Starts it
    Grants manager
    Brings
    export, notes, document
    Gets
    4 outputs

  • Goal alignment review

    Before next period's goals are set, the chief executive sees every team goal mapped to the company priority it serves: goals with no company parent, goals that pull against each other, priorities nobody owns, and the questions for each owner. It judges goals, never people.

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

  • Group room block pickup review

    As a group's room block nears its review or release date, the revenue manager and group-sales owner get one brief: rooms blocked, rooms confirmed, room nights still unfilled, counts that do not reconcile, and the questions for the account owner. A person decides any release or revised offer; the brief releases nothing.

    Starts it
    Revenue manager
    Brings
    export, notes, document
    Gets
    4 outputs

  • Headcount plan

    For a founder, people lead or finance lead preparing next year: every role and its cost by team, the new roles and backfills with their months, the fully loaded cost month by month against the budget, and what changes if revenue lands lower or higher. It plans roles and money, never decisions about named people.

    Starts it
    Finance lead
    Brings
    export, notes
    Gets
    5 outputs

  • Help article from a resolved issue

    Turn every answer your team works out once into an article the next customer finds on their own. Hand over a resolved ticket and your list of articles; get back a draft in your customers' words, with their details removed and every step traced to the ticket. Your knowledge-base owner decides what goes live.

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

  • Help centre gap review

    Once a period, your support lead sees what the help centre is missing, read from that period's tickets and search log: questions agents answered by hand, articles that fell short, articles search could not find, and one gap list ranked by the tickets an article could have saved. The lead decides what is written.

    Starts it
    Support lead
    Brings
    export, notes
    Gets
    6 outputs

  • Hiring pipeline status report

    Each week your people lead or founder sees every open role on one page: applications at each stage, days open against the target, roles running late, pass-through between stages, which sources lead to interviews, and every blocker with its owner. It counts; it never assesses a candidate.

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

  • Implementation blocker brief

    When a customer's setup milestone slips, the implementation lead gets one brief: the missing inputs, the unresolved access and data questions and the dependencies behind the delay, each with its source and an owner, plus points to raise with the customer.

    Starts it
    Implementation lead
    Brings
    export, notes
    Gets
    6 outputs