# White-label homepage preparation module

This is a **fictional portfolio sample**, not client work, a testimonial, or evidence of adoption. The company and product below do not exist. The sample shows the preparation layer a human copywriter, designer, or developer can purchase for a fixed $50 USDC and then edit under their own client process.

## Fictional brief

- Product: TraceDeck
- Public product category: hosted error-trace review for small software teams
- Primary buyer: technical founders and engineering leads at teams with 2–20 developers
- Desired visitor action: start a 14-day trial
- Publicly approved facts supplied for the exercise:
  - connects to GitHub and GitLab repositories;
  - groups repeated application errors into review queues;
  - links each group to a commit and affected release when source data permits;
  - supports Slack notifications;
  - Starter is $19/month and Team is $59/month;
  - the trial lasts 14 days and requires no card.
- Facts not supplied or verified:
  - time saved;
  - error-detection coverage;
  - security certification;
  - customer count;
  - uptime;
  - effect on incident frequency or revenue.

## Source and claim matrix

| Proposed message | Status | Editorial handling |
| --- | --- | --- |
| Connect GitHub or GitLab | Approved public fact | May state directly |
| Group repeated errors | Approved public fact | May state directly |
| Link groups to commits and releases | Conditional public fact | Preserve “when source data permits” near the claim |
| Start without a card | Approved trial fact | May state directly |
| Find every production error | Unsupported absolute | Exclude |
| Resolve incidents faster | Plausible but unmeasured outcome | Frame as workflow intent, not a result |
| Enterprise-grade security | No evidence supplied | Exclude; request evidence if strategically necessary |
| Prevent outages | Unsupported causal guarantee | Exclude |

## Buyer-path decision

The first screen should answer four questions in order:

1. What is TraceDeck? A hosted error-trace review queue.
2. Who is it for? Small software teams operating production applications.
3. What changes in the workflow? Repeated errors are grouped and tied back to available code/release context.
4. What can the visitor do now? Start a 14-day, no-card trial.

Implementation details and integrations support that decision; they should not displace it.

## First-pass page copy

### Hero

**Headline:** Turn repeated application errors into one review queue.

**Supporting line:** TraceDeck groups recurring errors, connects them to available commit and release context, and sends the queue to the small engineering team already responsible for the fix.

**Primary CTA:** Start the 14-day trial

**Secondary CTA:** See an example error group

**Trust line:** No card required. Connect GitHub or GitLab when you are ready.

### Problem

**Heading:** The same failure should not become five separate investigations.

Error alerts often arrive as isolated events. TraceDeck groups repeated occurrences so the team can review one pattern, its affected releases, and the code context available from the connected repository.

### Product workflow

**Heading:** From incoming error to an owned review item.

1. Connect a GitHub or GitLab repository.
2. Send application errors into TraceDeck.
3. Review grouped occurrences with available commit and release context.
4. Route selected updates to Slack and keep the queue moving.

No automatic-fix, complete-detection, or outage-prevention claim is implied.

### Offer

**Heading:** Start with the team you have now.

- **Starter — $19/month:** for one small product and its core review queue.
- **Team — $59/month:** for teams that need broader collaboration and routing.

The exact feature allocation between plans must be inserted from approved pricing documentation before publication.

**CTA:** Compare the plans

### Objection handling

**Heading:** Keep the repository connection proportional to the job.

The page should state the permissions requested, which repository data is stored, retention periods, deletion controls, and any subprocessors only after the product owner supplies approved facts. Do not replace those details with “secure,” “private,” or “enterprise-grade.”

### FAQ set

1. **Which repositories can I connect?** GitHub and GitLab are supported in this fictional brief.
2. **Does TraceDeck change my code?** No code-change capability was supplied or approved; the published answer must state the actual permission boundary.
3. **How are repeated errors grouped?** The product owner must approve a plain-language description before publication.
4. **What happens when commit or release context is unavailable?** The page should preserve that context appears only when source data permits.
5. **Do I need a card for the trial?** No. The fictional brief specifies a 14-day trial without a card.

## Metadata

- Suggested title: TraceDeck — Group repeated application errors for review
- Suggested description: Group recurring application errors, connect them to available commit and release context, and review the queue with your small engineering team. Start a 14-day trial without a card.

## Human-editor handoff

Before client delivery, the lead editor should:

- choose one voice direction and remove any language that conflicts with the client’s established terminology;
- confirm the Starter and Team feature allocation;
- obtain an approved permissions, retention, and deletion explanation;
- decide whether “small engineering team” matches the commercial segment;
- confirm the example-error-group secondary CTA can be implemented;
- replace all evidence placeholders with approved facts or delete the associated claim;
- run legal, privacy, and security review where the client’s process requires it.

## Acceptance checklist

- [x] One public product and one buyer path
- [x] Hero, core sections, CTA system, five FAQs, and metadata
- [x] Approved facts separated from assumptions
- [x] Conditional capability kept conditional
- [x] Unsupported absolutes removed
- [x] Human editor retains final voice and client approval
- [x] No credentials, private customer data, implementation, or performance guarantee

## Commercial boundary

The fixed $50 module supplies editable Markdown within two business days after complete intake and verified payment, with one factual clarification revision. It does not include client meetings, private-system access, implementation, final legal approval, or permission to contact the end client. The purchasing collaborator retains the client relationship and final editorial control.