Agreement
Scope, exclusions, payment, feedback, change control, ownership, and acceptance are written.
The Avorren process
See the important work before it gets expensive.
A strong process does not manufacture ceremony. It exposes decisions in the order that makes changing them least painful.
Discuss a projectTypical signature engagement · four to six production weeks after every start gate is clear
Before the clock starts
Four real start gates.
A target date becomes credible when money, authority, information, and access are real. Missing inputs pause the project rather than consuming family time or creating a false emergency.
Deposit
The 50% scheduling deposit has cleared. It is cash collected for work not yet fully earned.
Authority
One empowered approver can provide consolidated decisions for the client.
Inputs
Source content, evidence, brand files, access, and required people are available.
The working sequence
Strategy survives all the way to code.
Each stage produces something inspectable. You do not approve abstract adjectives, and Avorren does not disappear behind production before the direction is sound.
- 01
Frame the decision
The kickoff finds the commercial trigger: what changed, who needs to act, what makes the decision difficult, and what the current site fails to carry.
- Founder and stakeholder interview
- Audience, alternatives, objections, and proof
- Current-site and competitive review
- Written project brief and success measures
- 02
Choose the story
Positioning, page sequence, and core language are developed together. The client responds to a coherent argument rather than isolated headlines.
- Positioning and message hierarchy
- Website architecture and conversion path
- Core copy direction
- Evidence gaps named—not filled with claims
- 03
Make it tangible
A real visual direction shows how type, color, imagery, spacing, interface, and language behave on representative content.
- Homepage or key-page direction
- Light and dark behavior when useful
- Responsive principles
- One consolidated decision round before expansion
- 04
Build the system
The selected direction becomes a working site. Copy, design, implementation, forms, metadata, accessibility-minded behavior, and performance are treated as one product.
- Responsive page and component build
- Content entry and integration work in scope
- Analytics and measurement foundation
- Private preview on every supported viewport
- 05
Review what is real
Feedback happens in the browser through two consolidated rounds. Quality assurance is independent from the person who made the primary direction.
- Links, forms, browser, and device checks
- Keyboard, focus, structure, contrast, reflow, and reduced motion
- Performance and console review
- Scoped issues closed or recorded before acceptance
- 06
Accept and transfer
The client accepts the scoped work, clears the final balance, and receives control—not an indefinite dependency on the person who built it.
- Launch or controlled handoff
- Domain, hosting, code, forms, and analytics account map
- Known-good version and recovery notes
- Training, warranty boundary, and optional care choice
Keeping the work honest
Clear boundaries protect the result.
A premium engagement is not unlimited labor. It is a well-judged scope, enough iteration to make it excellent, and an explicit way to handle new information.
Two consolidated rounds
One empowered approver gathers comments and resolves internal contradictions before sending them.
$200 / hour, two-hour minimum
Work outside the agreement is described, prepaid, and scheduled before it begins. No surprise invoice and no invisible favor ledger.
Silence pauses the clock
Delayed content, access, or client decisions move the target date. Evenings, weekends, and protected family commitments do not become recovery capacity.
Client-controlled assets
Domain, accounts, source, content, and analytics stay accessible to the client. Care is useful only when it is chosen, not engineered as lock-in.
Named checks and known limits
Accessibility and performance work is recorded precisely. No certification, legal guarantee, or business-outcome promise is implied.
50% / 50%
Half schedules the work. The final half clears after scoped acceptance and before production launch or final transfer.
What you receive
The website—and the record behind it.
Exact documents vary with scope. A signature engagement is designed to leave enough evidence for the next owner, teammate, or vendor to understand what exists.
| Project brief | The business trigger, audience, position, success measure, scope, and open evidence gaps. |
|---|---|
| Content and design system | Approved core language, page architecture, visual rules, and reusable interface decisions. |
| Working website | The responsive implementation, configured integrations, metadata, and client-owned source. |
| QA and acceptance record | What was checked, what passed, what remains dependent on third parties, and the accepted final state. |
| Account map and handoff | Domain, hosting, forms, analytics, code, access owners, recovery path, and next responsible person. |
The right project can move quickly.