Grok capture brief

No download needed. Press Copy brief, then paste it into Grok. You can also select the text below and copy it yourself.
Complete recording instructions
# RoxyPM: updated-demo recording brief for Grok

Capture the real product doing useful contractor work. Deliver original recordings,
clean stills and a timestamped index. Do not build an ad, invent UI, rewrite a result,
or replace a failed action with a mockup. Use the updated RoxyPM demo tenant only.
The founder's other developer is maintaining demo data: do not reseed, purge,
change code, alter feature flags or change company-wide settings without coordinating.

## Read this before recording

- Record tenant-facing RoxyPM only. Keep administrative, technical and private
  settings out of the recording. Show the work the customer can do.
- Show residential construction, remodeling and the supported commercial
  tenant-improvement workflows only.
- Design Studio and material takeoff are not generally available. Leave them out.
  AI Renders and the designer portal are separate features and may be recorded.
- Confirm the refreshed tenant has coherent project names, dates, scope, prices,
  trade assignments and documents. If an important screen is empty or wrong,
  document it for the developer rather than manufacture a successful demonstration.
- Work inside an existing, designated recording project. If duplicates are needed,
  ask the owner to designate them. Do not alter someone else's active demo scenario.
- Use only clearly fictional sample documents and owner-approved demo contacts.
  Never expose real tax IDs, bank details, client addresses, private messages or
  personal contact details. Do not show authentication tokens in browser URLs.
- Emails, texts and invitations must go only to verified owner-controlled test
  destinations. Do not contact actual customers or subcontractors. Show the draft
  and confirmation screen if a safe test destination is unavailable.
- Sign only clearly labeled, nonbinding demonstration documents in a designated
  test flow. Payments must use a verified test/sandbox processor. If unavailable,
  show the checkout choices without submitting a charge. Do not fake Paid status.

## Recording format

Desktop: 1920 × 1080 minimum, preferably 2560 × 1440, 30 fps, browser at 100% zoom.
Capture a clean app window without tabs, bookmarks, OS notifications or address-bar
secrets. Keep text readable. Move the cursor deliberately, then park it away from
important content. Pause for 3 seconds before and after every meaningful state.

Mobile: a real supported phone, portrait, 1080 × 1920 or better. Capture taps,
microphone permissions and genuine camera/import behavior when relevant. No narrow
mobile emulation inside a large desktop recording. Lock orientation and silence
notifications. Capture clean native audio for the assistant demos.

For every priority workflow deliver:
1. One continuous, uncut recording including input, processing, review and result.
2. A clean 20–45 second excerpt, plus an 8–12 second result-focused excerpt.
3. Full-resolution PNG stills of input, review and saved result, at least 3 per flow.
4. A text transcript of everything spoken, with timestamps and speaker labels.
5. A manifest naming the tenant, role, project, capture date, source timestamps,
   observed result, pending verification and any edited-out waiting time.

No sped-up source masters. Keep the actual elapsed time. Edited excerpts may remove
waiting, but retain the original and mark every time cut. No music, fake waveforms,
extra notifications, fake cursors, animated success badges or AI replacement screens.
We will add branding and motion around the authentic footage later.

## Featured capture: screenshot to a filled-out lead

Capture this as a main workflow alongside voice and estimating. Use an owner-approved,
fictional kitchen-remodel inquiry in a text/email screenshot with a sample name,
controlled phone/email, project address and useful scope notes. Keep SAMPLE visible.

Show the source screenshot clearly, then New Lead > Photos > select screenshot >
Read All. Record the actual processing and the resulting filled-out lead form.
Pause on the extracted name, phone, email, address and notes. Review against the
source, correct a detail if needed, add anything missing, then save and reopen the
lead. Do not type the extracted fields in advance or stage a successful AI result.

Deliver desktop and dedicated portrait-mobile masters, plus readable stills of the
source, filled form before saving and reopened lead. Capture a separate photo of
handwritten notes or PDF example if it works cleanly. Do not claim every field can
be filled when the input does not contain it. Keep contact destinations controlled;
this flow needs no message sent to a real person.

Files: 00_screenshot-to-lead_desktop_master.mp4,
00_screenshot-to-lead_mobile_master.mp4, 00_lead-source.png,
00_lead-filled-form.png, 00_lead-saved.png. Deliver 20–45 second and 8–12 second
excerpts for the homepage, comparison pages and Facebook/Instagram edits, with
original timing and any removed waiting time recorded in the manifest.
Folder: 00_Screenshot_to_Lead.

## Priority 1: voice becomes work

Use the actual voice assistant, speaking naturally. Start with existing names in the
refreshed tenant. Substitute those names in these sample commands:

“On the [kitchen job], add a task for [cabinet sub] to confirm the cabinet delivery
on [future date]. Schedule my site meeting with [client] for [future date and time].
Draft an email to [controlled test recipient] with the meeting details.”

Capture the speech, the parsed actions, any clarification, the created task with its
project/assignee/date, the calendar event, and the email draft with its review/send
confirmation. Capture each resulting record after reopening it. A transcript alone
is not proof that the action happened. Preserve the real review step before a send.

Then capture short, separate examples: add a lead; record a material expense;
write a daily log; update a task; add a punch item; ask what is on the schedule.
Choose the best three additional actions that work cleanly. Show voice/personality
selection and two different voices, with matching human-spoken command and response.

Explicitly test “Create a new project for [demo customer] called [new demo name]”
through the regular tenant voice UI. New-project creation is NOT yet verified in
this capture brief. If it only updates an existing project or offers another route,
record the actual behavior and report it. Do not imply that every AI entry point
supports the same actions. Do not force unsupported actions through internal tools.

Files: 01_voice-multi-action_desktop_master.mp4, 01_voice-mobile_master.mp4,
01_task-saved.png, 01_calendar-saved.png, 01_email-review.png, 01_voice-choices.png.

## Priority 2: the estimate uses our knowledge

Use owner-approved sample scope, a sample completed contract and sample internal
cost sheet. Record the company-learning upload and the readable knowledge/rules
it actually learns. Show the company's terminology and pricing preferences, then
create an estimate from a real scope document, handwritten notes or photos of pages.

Capture input > processing > generated estimate > review > saved proposal. Show
specific corresponding examples: a term or scope phrase from the sample contract,
a price/rate from the cost sheet, and how each appears in the proposed work. If the
result does not demonstrate those connections, report that rather than claiming it.
Show the contractor's review and changes before the client-ready proposal.

Record one voice/text revision: change one clearly identified material or scope
item, inspect the proposed edits, save and show what stayed unchanged. Capture the
proposal presentation without internal costs or markup exposed to the customer.

Eric's anecdote: he reports a $500,000 estimate that took a week by hand and about
15 minutes in RoxyPM. This is his experience with one estimate. Do not stage that
job as an independently measured benchmark. If Eric supplies the actual approved
example, record it with his permission and retain the real timing; otherwise use a
normal demo estimate and label it accordingly.

Files: 02_company-learning_master.mp4, 02_scope-to-estimate_master.mp4,
02_input-scope.png, 02_learned-pricing.png, 02_estimate-review.png,
02_client-proposal.png, 02_selective-revision_master.mp4.

## Priority 3: business card to onboarded subcontractor

Start with a clearly marked fictional SAMPLE business card using an approved test
identity and controlled inbox. On mobile, photograph the physical sample card if
available. On desktop, import the sample image through the tenant's AI Import Sub.

Capture the card > extracted name/company/trade/contact information > review >
saved subcontractor record. Then launch onboarding from that record. Show the
package with agreement, W-9 and insurance requirements, review it and send only to
the controlled test destination. Do not describe a signed agreement as being
created by the card import alone; the sub completes the next steps.

In the sub-facing test portal, show the nonbinding sample agreement signing flow,
a fictional sample W-9 and sample insurance upload. Return to the contractor view
and show the resulting statuses and documents attached to the right sub. Capture
insurance-expiry information if the uploaded sample actually produces it.

Files: 03_card-to-sub_master.mp4, 03_sub-onboarding_master.mp4,
03_business-card.png, 03_import-review.png, 03_onboarding-package.png,
03_sub-signing.png, 03_paperwork-complete.png.

## Priority 4: customer signs and pays

Use one coherent estimate/project, not different records between shots. Show the
client's branded portal, proposal review, e-signature and the retained signed
version. Then show the deposit/invoice and payment choices. Complete a transaction
only in a verified sandbox. Capture the customer confirmation and the contractor's
updated payment record if the test payment really succeeds.

If sandbox payment is unavailable, stop before submission and deliver the checkout
recording with that limitation in the manifest. Show the customer's view directly,
not just the contractor's portal configuration screen.

Files: 04_client-sign-and-pay_master.mp4, 04_client-proposal.png,
04_signature-review.png, 04_signed-document.png, 04_payment-options.png,
04_payment-confirmed.png (only if a real sandbox result exists).

## Priority 5: walkthrough to useful scope

Use a real project photo or designated demo room and the actual site Walkthrough
button. Speak a clear description of existing conditions and requested work.
Capture the raw walkthrough, organized notes/scope and the estimate handoff. Keep
any generated room visualization labeled as an AI render, never a finished job.

Files: 05_walkthrough-to-scope_master.mp4, 05_walkthrough-input.png,
05_organized-scope.png, 05_estimate-handoff.png.

## Supporting recordings

6. Designer and client: designer submits a selection/file, contractor reviews cost,
   client makes their separate decision. Show role differences with the same item.
7. Vendor: order, delivery update and invoice submitted from the vendor's view,
   followed by the contractor's review and the bill on the correct job.
8. Client confirmation: invitation to a site meeting, the customer's confirmation
   or reschedule request, and the contractor's updated appointment state.
9. Background checker: a fictional/approved demo case, sources and useful context.
   Do not depict it as a certified criminal or credit report or use a real person's
   sensitive background information for marketing.
10. AI learning over time: show an actual saved correction or company preference
    followed by a later draft that uses it. Do not invent a success result or
    relabel the empty training screen as proof of continuous improvement.
11. AI Renders: real source photo, requested design, actual output and shared slider.
    Mark the output as a visualization. This is separate from Design Studio.
12. Finish with clean, populated dashboard, lead pipeline, estimate, project task
    list, calendar, sub list, vendor list and client portal stills, desktop and mobile.

## Quality gate before delivery

Every published claim must have a matching captured result or be marked unverified.
Check names, addresses, dates, task assignments, prices and document statuses for
continuity. No empty/QA records, stale brand styling, unrelated product menus,
notification popups, other browser tabs or personal data. Do not create sensitive
fictional paperwork that could be mistaken for genuine documentation: sample
marks must remain visible. Keep all source masters intact.

Deliver organized folders: 01_Voice, 02_Estimating, 03_Sub_Onboarding,
04_Client_Sign_Pay, 05_Walkthrough, 06_Supporting, 07_Stills, plus manifest.csv and
transcripts.txt. Report any blocker by exact screen/action and observed result.
Do not silently skip an unsuccessful workflow.

SOCIAL EDITING FORMATS
Preserve full-resolution originals. We will create 1080 x 1920 vertical edits,
1080 x 1350 feed edits and 1920 x 1080 website edits. Keep the input, review and
result readable. Capture separate desktop and mobile masters instead of cropping
a desktop screen into an unreadable phone-shaped sliver.

REPLACEMENT PASS: SEPTEMBER 16 OWNER REVIEW
Every existing app still, app clip and screenshot-based marketing creative is an
interim asset. Replace them throughout the homepage, features, SEO/trade pages,
comparisons, video watch pages and social edits after the refreshed capture is reviewed.
Start with the dashboard used in the hero and voice section: use a fully configured
demo company with the setup process complete. Do not retouch or fake a completed state.
Capture coherent, populated project records whose cover photos actually match the job.
The previous Park project capture showed an unrelated woodland cover; do not repeat it.
Capture the real client-facing portal, not only the contractor's portal controls.
Capture completed voice actions, reviewed estimates with learned pricing, sub import
and onboarding, and client signing/payment as described above. Settings screens alone
do not replace workflow proof. Keep original sources and timestamped provenance.
Do not include Eric's portrait or crew/jobsite photos containing people in new marketing
exports. Keep authentic project-only photography and the approved, labeled before/after
comparison. Capture that slider from the owner's shared example:
https://app.roxypm.com/ba/NgIoBPMWYS2D
Show the full original, a centered comparison, the full AI concept, and full-screen view.

PROJECT PHOTO ALLOCATION
No original project photo may appear more than once on a page or on more than two
marketing/media pages overall. Crops, exports and photos inside social films count
as the same original. Use src/marketing/photo-plan.json and run the photo audit when
replacing assets. Keep a video's cover with that video; avoid reusing its project
photos elsewhere. Preserve the homepage before/after immediately after the hero.