Worked project example
See the sources. Check the brief.
Follow a fictional status brief from source records to a reviewable draft. See the inputs, the prompt and the checks, then adapt the method to your own work.
Fictional teaching example. Not a customer case study, a live product run or a promise of results.
1. Start with a small, named source set.
All records below are invented for this example. The scope is these three records only, not a complete team or reporting period. No snapshot date was supplied.
EX-01: Onboarding checklist
- Status: done.
- Owner: Operations lead.
- Due date: not provided.
- Note: final checklist saved.
EX-02: Campaign outline
- Status: ready for review.
- Owner: Marketing lead.
- Due date: not provided.
- Note: reviewer feedback needed.
EX-03: Pricing FAQ
- Status: blocked.
- Owner: not provided.
- Due date: not provided.
- Note: waiting for approved plan details.
For your own run, use approved records you are allowed to share. Include stable source references and snapshot dates when available. Do not include sensitive data the task does not need.
Copy and adapt
2. Ask for a draft with boundaries.
For this teaching example, supply the three sample records above with this prompt. Replace them with approved sources for your own workflow.
Goal: draft a status brief from EX-01, EX-02 and EX-03 only. Output: completed work, work ready for review, blocked work and missing information. Cite the source ID for every status statement. Keep suggested next actions in a separate section. Do not invent owners, due dates, completion dates, results or a reporting period. Do not treat ready for review as completed. Flag the missing snapshot date and explain the coverage limit. Permissions: read and draft only. Do not send messages, publish, change records, create a schedule, buy data or spend money. Review: show the sources checked, what is unknown and what the reviewer should confirm. If a source is unavailable, name it rather than guessing.
3. Compare an illustrative draft with its sources.
Illustrative draft, written for this example. This is a model of the output to request, not evidence that an automated run produced it.
Completed work
The onboarding checklist is marked done, and its note says the final checklist was saved. Recorded owner: Operations lead. No completion date was supplied. Source: EX-01.
Ready for review
The campaign outline is ready for review, with reviewer feedback needed. Recorded owner: Marketing lead. This is not recorded as completed. Source: EX-02.
Blocked work
The pricing FAQ is blocked while it waits for approved plan details. No owner or due date was supplied. Source: EX-03.
Unknowns and coverage
The records have no snapshot date, so this brief cannot establish their current status or claim to cover a particular week. No due dates were supplied. Coverage is limited to EX-01, EX-02 and EX-03.
Suggested next actions, not recorded commitments
- Confirm the snapshot date and whether any records are missing.
- Ask who should review the campaign outline.
- Confirm the pricing FAQ owner and the source for approved plan details.
No messages have been sent and no source records have been changed as part of this teaching example.
Review before repeating
4. Check the work, not just the wording.
Use these checks on the actual output of your first run. This example does not establish accuracy, time savings or business results.
Trace every status
Open the source behind each statement. Check that ready for review stayed separate from done, and that a source note did not become an invented outcome.
Keep unknowns visible
Check that missing owners, dates and coverage remain unknown. Suggestions must not look like assignments or commitments.
Repeat only after review
Correct the brief first. Consider a Scheduled Project only after a useful run, with supported sources and triggers. Sending, publishing, record changes and purchases keep their separate controls.
Check the tools available to your project.
SalesHive projects work with the tools and accounts available to that project. A connector listing does not mean every action in the app is supported. Review Projects and Scheduled Projects and connected apps, tools and permissions before choosing a workflow.
Use the first-project brief to define your own sources, output and success check. Expert implementation is optional. If you need a team to run outbound, managed cold calling and managed plan pricing remain available.
Scope your first workflow
Bring one recurring job to the conversation.
Bring the source types, who will review the output and an example of a useful result. We can help check what is supported today and discuss optional implementation. Confirm scope and any cost before work starts.