# ScopeLatch Studio Kit — free sample

One of 12 project presets and one of 8 client emails from the Studio Kit.

Hours illustrate hands-on effort for an experienced solo designer/developer using one familiar site builder or CMS and existing components. They are not market averages, fixed quotes, elapsed delivery times, or promises. Discovery can change them. Estimates include only the stated quantities. Client waiting time, subscriptions, assets, tax, and third-party fees are excluded.

## Single-offer landing page

**Best for:** One campaign, one audience and one primary conversion action; useful when the offer is already decided.

**Illustrative hands-on effort:** 24 hours.

### Scope assumptions

- One public page with up to eight sections, plus links to client-supplied policy pages.
- One lead form with up to five fields and one existing destination or email notification.
- Client supplies approved copy, brand assets and an existing analytics account.
- One design direction; one structural and one visual/content revision round.

### Deliverables and effort

| Deliverable | Quantity and boundary | Illustrative hours |
|---|---|---:|
| Offer and conversion brief | One 45-minute discovery session and one-page brief identifying audience, offer, CTA and objections | 2 |
| Section map and wireframe | One page, maximum eight sections, one structural review | 3 |
| Responsive visual design | One visual direction with desktop and mobile layouts, one visual review | 5 |
| Page implementation | Build approved sections and reusable button/form styles on the agreed platform | 7 |
| Lead form and confirmation | Up to five fields, validation, one confirmation state and one destination test | 2 |
| Basic measurement setup | Connect existing analytics and verify one primary conversion event when account access and consent requirements are supplied | 2 |
| QA and launch | Responsive and keyboard checks, link audit, one domain launch and handoff note | 3 |
| **Total** | | **24** |

### Concrete exclusions

- Offer strategy, long-form copywriting or customer research.
- Additional campaign variants, A/B tests or paid ad management.
- Custom CRM automation, lead scoring or multi-step forms.
- Checkout, accounts, custom calculators or gated downloads requiring a backend.
- Legal/policy drafting, consent strategy and guaranteed conversion improvements.

### Client inputs

- Primary conversion action and the destination of submitted leads.
- Final section copy, three approved proof points and permission to use any testimonials.
- Logo, colours, fonts and licensed images.
- Domain, platform, form destination and analytics access through appropriate invitations.
- Named decision-maker and the required policy/consent text.

### Review checkpoints

- Approve the offer, CTA and section list before design.
- Approve the wireframe before detailed visual work.
- Submit one consolidated visual/content revision list before build completion.
- Run a test lead together and confirm the real receiving destination before launch.

### Acceptance checklist

- [ ] All approved sections are present in the agreed order.
- [ ] The primary CTA is visible and points to the agreed action.
- [ ] A valid form submission reaches the named destination; invalid input displays a useful message.
- [ ] Confirmation text explains the next step without promising an unapproved response time.
- [ ] The page has no horizontal overflow at agreed test widths and supplied controls work by keyboard.
- [ ] The agreed event appears in the analytics test view, or an account/platform limitation is documented.
- [ ] Page title, description, favicon, policy links and social preview content match approved inputs.

### Common change triggers

- A second audience or offer needs a distinct page.
- The client replaces the approved conversion action or adds a checkout.
- A requested integration requires custom authentication or API work.

## Client email: price a new request

**Use when:** A request adds work beyond the current scope and you have enough information to estimate it.

**Subject:** [Project] — options for adding [request]

Hi [Name],

You asked to add [plain-language request]. The current scope includes [relevant existing deliverable]. This addition would require [specific new work], including [testing/content/dependency].

I've outlined it in change request [ID/version], attached. The options are:

- **Add it now:** [deliverables], for [currency/amount or capped estimate], with [schedule impact and assumptions].
- **Keep this release as planned:** complete the existing scope, then schedule the addition for [later decision point].
- **Swap scope, if useful:** remove [specific unstarted work] and add [specific requested work], with [net price/time impact]. [Delete this option if no real swap is available.]

My recommendation is [option] because [reason tied to their goal]. Please reply with the option you want and any corrections to the request. I will not start the added work until the scope, price and timing are confirmed through our agreed approval process.

The already-approved [unaffected task] can continue as planned.

Thanks,
[Your name]

**Before sending:** Do not offer a scope swap unless the removed work has not already been completed or committed. Include third-party costs and dependencies separately.

## Using this sample

You may adapt these original materials for your own business and client work. Do not resell or redistribute them as a competing template pack. These are planning materials, not legal contracts.

Full kit details: https://scopelatch.tech/studio
Support: support@scopelatch.tech