Free project brief

Choose one job. Make the first run useful.

Turn a recurring task into a clear SalesHive project brief. Choose an output, name the sources and set the boundaries before you automate anything.

Get the briefTalk through your workflow

No signup needed to read or copy this resource. Expert implementation is optional.

Start small

Pick an output you can check.

These are starter ideas, not promises of an integration or a result. Use sources you are allowed to share, and check the available tools for each connected app.

Sales: a meeting-prep brief

Use an upcoming meeting and approved account notes. Ask for the goal, known context, open questions and source links. Keep outreach and CRM changes out of the first run.

Learn more

Marketing: a content outline

Use approved product facts and customer questions with permission. Ask for an outline with supporting sources and unsupported claims flagged. Review it before any publishing.

Learn more

Operations: a weekly status brief

Use an approved task export or connected task records. Ask for completed, upcoming and blocked work. Include owners and dates only when the source records them.

Learn more

Copy and adapt

Your first-project brief.

Replace the brackets, then use the brief in a new SalesHive project. Remove sensitive information the task does not need. The first run is deliberately read-and-draft only.

Goal: [one recurring job and who uses its result].
Sources: [approved files or exact records, connected apps and date range].
Output: [a brief, table or draft, including the fields and source references it must contain].
First run: use only the sources and tools already available to this project. Check access before starting. If an input or tool is missing, name it and stop that part of the work.
Permissions: read and draft only for this first run. Do not send messages, publish content, change records, buy data or spend money.
Quality rules: do not invent facts, statistics, quotes, owners or dates. Label missing evidence and separate facts from suggestions. Respect consent and suppression rules.
Review: show the result, the sources checked, missing coverage and anything I need to decide. Do not create a recurring schedule yet.
Success check: [the person who reviews it, what makes the output useful and how it will be checked].
Possible repeat: [frequency or event to consider only after a useful first run].

Before it repeats

A useful draft comes before automation.

Use this checklist to decide whether the work is ready for a repeat run. It is a review method, not a guarantee of accuracy or savings.

  1. 1

    Check the sources and access

    Open the available inputs and confirm the agent can read what the task needs. For connected apps, review the individual tools and permissions. A listed connector does not support every action in that app.

  2. 2

    Check the actual result

    Compare the brief, table or draft with the original records. Verify the facts and links. If coverage is incomplete, narrow the task or supply the missing source rather than accepting a confident guess.

  3. 3

    Record one correction

    Tell the project what was missing or unhelpful. Make the success check specific, such as every status item linking to its source and no unsupported owner or date.

  4. 4

    Choose whether to repeat

    Once the result is useful, consider a Scheduled Project. Client projects can start on a timer, manually, from a supported connected-app event or after another schedule finishes. Available triggers depend on access and the app. Keep send, publish and purchase controls separate from the schedule.

Check the product, not a promise.

SalesHive projects use the tools and connected accounts available to that project. Reading and making changes have separate controls, and existing approval requirements still apply. Review the current guides before choosing the workflow:

Need a team to run outbound instead? Managed cold calling and managed plan pricing remain available.

Optional expert implementation

Bring a workflow, not a finished specification.

Bring the job, the tools involved, who reviews the output and one example of a good result. We can help scope the workflow and check what is supported today. Confirm the scope and any cost before implementation starts.

Talk through your workflowExplore implementation help