Book a fit call

Workflows Directory

Find your team’s next superpower.

Results

192 workflow templates, showing 145 to 168

  • Sales call preparation brief

    Your salesperson, partner or account manager walks into every meeting with a brief they can read in five minutes: who will be there, what has been said and promised so far, what is still open, and a plan for the call. Every line traces to your own notes or a public page, and anything inferred is labelled.

    Starts it
    Salesperson
    Brings
    notes, pasted text
    Gets
    7 outputs

  • Sales call scorecard

    After a sales call, your sales lead sees how it went against your team's own criteria, each point backed by the words actually said, where the call left the deal, and one focus for the next call. It reviews a call, never a person, and gives no score for anyone's file.

    Starts it
    Sales lead
    Brings
    export, notes
    Gets
    5 outputs

  • Sales proposal preparation

    Your account executive answers an RFP in minutes, not weeks, with a proposal draft where every claim traces to approved company information and every gap is already a question for the right person.

    Starts it
    Account executive
    Brings
    document
    Gets
    4 outputs

  • Schedule recovery options

    When a committed milestone slips, the project manager brings the sponsor two to four ways back: what each changes, the dates it gives every later milestone and dependency, and the assumptions it rests on. The sponsor chooses; delivery leads confirm the dates.

    Starts it
    Project manager
    Brings
    export, notes
    Gets
    5 outputs

  • Scope change impact review

    When new work turns up in a project plan, the project manager gets one review: every deliverable compared with the agreed baseline, each addition marked approved or not, its estimated effect on effort, cost and the end date, and the decision the sponsor has to make. The sponsor accepts or declines each one.

    Starts it
    Project manager
    Brings
    export, notes, document, pasted text
    Gets
    6 outputs

  • Search exclusion conflict check

    The paid search specialist gets a list of live keywords that a live exclusion may be blocking, each with the level where the exclusion applies and the campaign intent it touches. They are clues from the text; the specialist decides what to change.

    Starts it
    Paid search specialist
    Brings
    export, notes
    Gets
    5 outputs

  • Service inbox routing plan

    When a new service inbox is being set up, the service owner gets a routing plan: each approved address, the queue it should reach and who owns it, checks to run before it goes live, and the wrong-address risks, loop risks and unconfirmed queue owners still open. Nothing is configured.

    Starts it
    Service owner
    Brings
    export, notes
    Gets
    5 outputs

  • Service provider evidence matrix

    When a material service provider needs approval or renewal, the vendor owner gets one matrix: the provider's evidence set against the firm's own review criteria, with self-attestations, dated reports and untested claims kept apart from independent evidence, and every unanswered question listed.

    Starts it
    Vendor owner
    Brings
    export, notes
    Gets
    4 outputs

  • Service roster options

    For a department manager building a rota for expected occupancy, covers or events: two or three roster options side by side, with each role's need, the staff confirmed available, the periods left uncovered and the labor-cost assumptions you supplied. You verify and approve; nothing is published.

    Starts it
    Department manager
    Brings
    export, notes
    Gets
    5 outputs

  • Shared folder filing plan

    The office coordinator gets a plan for tidying a shared folder: a proposed folder structure, every file's move with its owner named, and the duplicates and access questions to settle first. Owners approve their own moves; nothing is moved, renamed or deleted.

    Starts it
    Office manager
    Brings
    export, notes, document
    Gets
    6 outputs

  • Site observation follow-up

    After a site visit, the visiting engineer and the project manager get one observation report: each field note beside its location, source photograph, drawing revision and any earlier register entry, a proposed follow-up owner, and the questions still open. It assesses no condition.

    Starts it
    Visiting engineer
    Brings
    export, notes
    Gets
    5 outputs

  • Slow-moving stock and markdown plan

    Before a seasonal reset, the merchandiser or store owner gets one plan from the sales and stock exports: each item's sell-through and weeks of cover, the cash tied up in dead and slow stock, and a markdown plan in dated steps with the margin each leaves and a date to stop. The owner decides every price.

    Starts it
    Merchandiser
    Brings
    export, notes
    Gets
    5 outputs

  • Smallest useful release scope

    A product owner or founder with more features than capacity gets one page: what is in the first release and what is deferred, all tied to one user outcome, with the reason for each cut. The owner decides the scope; no effort is estimated beyond what is supplied.

    Starts it
    Product owner
    Brings
    export, notes
    Gets
    7 outputs

  • Spreadsheet check before sharing

    Before a model or schedule goes to a client, a lender or a board, the sender gets one report on it: every error value, short total, buried assumption and hidden row pinned to its cell, each with a fix or a question, and a plain list of what was not checked. Nothing in the workbook is changed.

    Starts it
    Finance manager
    Brings
    export, notes
    Gets
    5 outputs

  • Staff newsletter and FAQ roundup

    Each month the office manager turns what teams send in into one staff newsletter, with answers to the questions people keep asking, each quoted from an approved source and its owner named. Nothing about one person's pay, health or performance goes in, and a person approves the issue before it goes.

    Starts it
    Office manager
    Brings
    export, notes, document
    Gets
    2 outputs

  • Stale ticket sweep

    Once a week the support lead gets one sheet of what the queue is hiding: tickets with no real activity past their limit, tickets left waiting on the customer with the three ways out of each, likely duplicates, and each person's load weighed by size and age. A person makes every move.

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

  • Stalled-deal review

    Your sales lead sees, from the record alone, which open deals have stopped moving, what each one's stage still lacks and whose move it is, and where every recent no ended and why. Nothing in your sales system is changed; corrections are proposed for a person to make.

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

  • Stock count reconciliation

    After a physical count, the bookkeeper and the warehouse or store lead get every item counted beside the quantity and value in the books, each difference in units and money, what to check for it, and the items to recount. Nothing is adjusted until a person approves.

    Starts it
    Bookkeeper
    Brings
    export, notes
    Gets
    5 outputs

  • Store facts file

    The person who runs an online store builds the one file every other store workflow template reads first: what the store sells, the facts each product page should state, the statements it stands behind, buyers' questions, policies, roles and access. Nothing on the store is changed.

    Starts it
    Owner
    Brings
    export, notes, document, pasted text
    Gets
    2 outputs

  • Store guide for AI shopping assistants

    The person who runs an online store gets the plain-language guide a shopper's AI assistant reads about the store: what it sells, for whom, which product line suits which need, and where the policies are. Every line traces to the approved store facts file, and a person places it.

    Starts it
    Operator
    Brings
    document, pasted text
    Gets
    6 outputs

  • Submittal register review

    The project engineer gets one register of every required submittal: what has arrived, the review status as recorded, the documents still missing and the long-lead items at risk against the date each order must be placed. Nothing is routed, accepted or ordered.

    Starts it
    Project engineer
    Brings
    export, notes
    Gets
    6 outputs

  • Subscription billing exception sheet

    Before a subscription billing run, or when a customer disputes a charge, the billing specialist gets a sheet tying each account's plan, quantity and invoice lines to the approved price mapping and the seat or usage records, with doubtful matches kept open.

    Starts it
    Billing specialist
    Brings
    export, notes
    Gets
    7 outputs

  • Supplier bill review and payment-run preparation

    Before each payment run, the person who approves it gets one sheet: every supplier bill checked against its purchase order and what was received, duplicates and changed bank details stopped, credits shown, and a proposed run with its total. Nothing is paid until a person approves.

    Starts it
    Payables clerk
    Brings
    export, notes
    Gets
    7 outputs

  • Supplier delivery date check

    The purchasing or operations person gets one comparison from the open purchase orders and the supplier replies: promised and revised dates side by side, the orders each change puts at risk, and the follow-ups still unanswered. No supplier is contacted.

    Starts it
    Buyer
    Brings
    export, notes
    Gets
    5 outputs