Book a fit call

Workflows Directory

Find your team’s next superpower.

Results

243 workflow templates, showing 193 to 216

  • Renewal risk review

    Once a month, the account manager sees every contract coming up for renewal on one page: the dates that matter, the warning signs your organization watches for, which accounts are at risk, and the next step for each with an owner and a date. A person decides and makes every contact.

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

  • Research plan for counsel

    Before an associate or paralegal starts on a partner's research question, they hold a one-to-two-page plan: the question split into sub-questions, the stated facts against each, the firm's own notes to read first, where to search and with what terms, and the gaps. Leads, not authorities: nothing is named from memory.

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

    Prepares work for a lawyer. Not legal advice.

  • Restricted gift rollforward

    The finance lead gets a working schedule for one named restricted fund: opening balance, recorded gifts, coded expenditure and closing balance, with every unresolved difference listed from the gift agreement summary and the ledger detail. Nothing is posted.

    Starts it
    Bookkeeper
    Brings
    export, notes
    Gets
    6 outputs

  • Roadmap tradeoff review

    When a new priority arrives, the product owner sees what the roadmap would have to give up to hold it: the capacity gap by team, the work that could move, the commitments and dependencies that move with it, and the questions still open. The owner decides.

    Starts it
    Product owner
    Brings
    export, notes
    Gets
    8 outputs

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

    Each week your sales lead sees the whole open pipeline on one page: value and age by stage, what moved since last week, the deals at risk and coverage against your target. Every figure traces to your export, and the forecast number is left for a person to commit.

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

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

  • Service visit work packet

    Before a planned visit to a turbine, inverter or terminal asset, the maintenance supervisor gets one packet built from the logs and approved scope supplied: reported symptoms, previous visits, open parts requests and access questions. It judges no condition and sends nothing.

    Starts it
    Maintenance supervisor
    Brings
    export, notes
    Gets
    7 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

  • Software subscription and vendor spend review

    From a card statement or ledger export, the finance or operations lead gets every subscription on one register: what each costs a year, who owns it, what renews in the next 90 days, what looks unused, duplicated or orphaned, and the decisions to make. Nothing is cancelled or changed.

    Starts it
    Finance lead
    Brings
    export, notes
    Gets
    9 outputs

  • SOP exception capture

    Turn what your most experienced person does with the awkward cases into an exception register for one procedure. Once the owner approves it, every colleague handles those cases the way your best person does.

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

  • 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