Book a fit call

Workflows Directory

Find your team’s next superpower.

Results

138 workflow templates, showing 49 to 72

  • CRM field ownership map

    Before a CRM sync or field mapping changes, the systems owner gets a field map from the supplied exports and sample records: each field's source, match keys and conflict rule, with unclear keys, consent fields and duplicates left as questions for each field's owner.

    Starts it
    Systems owner
    Brings
    export, notes
    Gets
    7 outputs

  • Culture health check

    A founder or people lead sees whether the company's stated values show up in daily work: each value written as behaviours you could watch for, read against the team's own evidence, with where practice matches, where it drifts, and two or three rituals to try. Reported by team and theme, never about a person.

    Starts it
    Founder
    Brings
    export, notes, document
    Gets
    7 outputs

  • 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 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 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

  • Dated stock exposure list

    Before the next production or replenishment order, the supply planner gets a batch-by-batch list of stated dates, quantities and locations set against each retailer's acceptance rules, showing which batches need a decision. The quality owner and supply lead decide.

    Starts it
    Supply planner
    Brings
    export, notes
    Gets
    5 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

  • 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

  • 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 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

  • 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

  • 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

  • Inbound demand or claim intake record

    When a demand, claim or subpoena arrives, the company's lawyer gets one intake record the same day: who sent it, what it asks, every date it states, the facts and citations it relies on, related matters, where the records are, and a question on keeping them. It rates nothing and recommends nothing.

    Starts it
    Legal operations coordinator
    Brings
    export, notes, document
    Gets
    2 outputs

    Prepares work for a lawyer. Not legal advice.

  • Inbound receiving exception trace

    When what arrived does not match the advance shipment notice, the receiving supervisor or inventory controller gets the notice, the packing list and the scans side by side by item and lot, with missing references and questions to investigate. Nothing is adjusted and nobody is contacted.

    Starts it
    Receiving supervisor
    Brings
    export, notes
    Gets
    5 outputs

  • Inherited campaign audit

    When an agency takes over an account or prepares a campaign health review, the media or analytics lead gets an inventory of what is running against the client's plan: mismatched offers, disagreeing destination pages, missing measurement evidence, and an owner for each follow-up.

    Starts it
    Media lead
    Brings
    export, notes
    Gets
    6 outputs