How projects move from the first conversation to launch.

The work is scoped before production begins, required inputs are confirmed, and changes are discussed before they affect cost or timing.

Four stages establish the work, responsibilities, and next decisions.

The stages show the order of the work, not a fixed number of meetings. A stage may require one conversation or several rounds of review, depending on the decisions and information involved.

  1. 01

    Discovery and direction

    We discuss what is happening now, who it affects, what the project needs to accomplish, and any constraints or dependencies that must be considered.

    This stage establishes

    An agreed purpose, audience, priorities, and any questions that require further investigation.

  2. 02

    Scope and proposal

    I translate the agreed direction into specific deliverables, responsibilities, exclusions, timing, and project cost.

    This stage establishes

    An approved scope and fixed project proposal showing what is included and what each of us is responsible for providing.

  3. 03

    Readiness

    You provide the content, assets, information, access, decisions, and approvals identified in the proposal. I review those inputs and confirm whether production can begin.

    This stage establishes

    A confirmed starting point based on the actual project materials rather than assumptions.

  4. 04

    Production and launch

    I create the approved work, conduct the planned reviews and quality checks, complete the agreed refinements, and prepare the project for launch and handoff.

    This stage establishes

    A completed release with ownership, documentation, support, and next steps identified.

Not every need ends at launch.

Fractional Digital Partner engagements use the same discipline around priorities, responsibilities, access, documentation, and changes, but work from an agreed ongoing backlog/capacity rather than a single fixed deliverable.

Explore Fractional Digital Partner support

Project pricing is based on the scope of the work being approved.

As a general guide: a single-page site starts at $1,200. Most multi-page business sites run $6,000 to $8,000. Projects with ecommerce, events, a gallery, or a lightweight CRM built in can run up to $15,000. After the necessary discovery, you receive a fixed proposal. The price reflects the approved scope, including:

  • Deliverables and content readiness
  • Required functionality
  • Connections with other systems
  • Data and migration needs
  • Testing and documentation
  • Launch and support requirements

Third-party services or expenses are identified separately. If the scope changes, the effect on cost and timing is presented for approval before the additional work begins.

When an existing process or system must be investigated before the scope can be responsibly defined, discovery may be proposed as its own paid phase. You will know that before the discovery work begins.

More detail, when you want it.

The primary stages above are the essential path. These sections explain responsibilities, reviews, quality checks, and handoff in greater depth.

Fit and discovery

After reviewing your inquiry, we begin with a focused conversation about the business need, intended users, current approach, constraints, and timing. Discovery may also include reviewing existing tools, content, information, or processes.

Once the relevant questions are resolved, I can define the scope. When material uncertainty prevents that, I may recommend a separate paid discovery phase before preparing the full project proposal.

Responsibilities and readiness

Your proposal spells out what’s on you, what’s on me, and what needs sign-off before production starts.

You may be responsible for:

  • Approved content, images, documents, or data
  • Access to the accounts and systems involved
  • The business decisions only you can make
  • One consolidated set of feedback, not five separate ones
  • Sign-offs, on the schedule we agree to

Digital Done Right is responsible for:

  • Flagging what’s needed and what’s still unresolved
  • Building everything in the approved scope
  • Raising real questions, risks, or changes as they come up
  • Testing the work at the level the project actually needs
  • Getting launch and handoff materials ready

Once the required inputs are in and approved, the production schedule is confirmed.

Reviews and scope changes

Planned reviews compare the work with the approved scope. Feedback should be consolidated through the agreed decision-maker so refinements can be evaluated and completed consistently.

Refinements within scope are handled during the agreed review rounds. Requests that change the approved direction, deliverables, functionality, or timing are documented as scope changes.

Any effect on price or schedule is presented for approval before the additional work begins.

Quality checks, launch, and handoff

Final checks are selected for the type of work being delivered. They may cover content accuracy, links, forms, behavior across relevant screens, accessibility, workflow rules, permissions, connections with other systems, performance, and what happens when something fails.

Launch takes place after the required reviews and approvals are complete. The handoff identifies access, ownership, documentation, training, maintenance, and any ongoing support included in the project.

Begin with the business context.

Use the project inquiry form to describe the current situation, the people affected, and the result you need. A completed scope is not expected at this stage.

Start a project inquiry