← Growth Services

Custom growth project

Create interactive assets worth finding, using and citing.

Build calculators, quizzes and assessments when an interactive experience can create more decision value than another static article.

Typical timeline: 4–6 weeks · fixed price agreed after scoping

Typical project scopeDefined before work begins
  1. 01Use-case design
  2. 02Logic and data model
  3. 03UX/content structure
  4. 04Development
  5. 05Lead capture where appropriate
  6. 06Measurement

When to use it

Scope this separately when the opportunity is concentrated enough to deserve a project.

Growth Services sit beside managed search work rather than inside every retainer. The goal is to make scope boundaries clearer, not to create surprise add-ons.

01

The audience has a repeatable decision that can be modeled.

02

A useful tool can create differentiated information gain.

03

The funnel needs a higher-value engagement asset.

Project model

Evidence → scope → build → verify.

01

Define the constraint

Start from the search, funnel or operational evidence that justifies the project.

02

Lock the scope

Agree the deliverables, required inputs, acceptance criteria and limits on included work.

03

Implement

Build the agreed work without silently expanding into unrelated tasks.

04

Verify

QA the output and, where measurable, reconnect it to the visibility or conversion signal that started the project.

Deliverables

What you receive.

Use-case and concept brief

A definition of the decision the tool helps users make, who it serves, the search demand around it and how it fits your funnel.

Logic and data model

The formulas, scoring rules or decision paths behind the tool, documented and checked by your subject-matter expert before build.

UX and content structure

Wireframes for inputs, results and explanations, plus supporting page copy that helps the tool rank and makes its results easy to understand.

Built tool

A working calculator, assessment or quiz embedded on your site, responsive and accessible, with results that users can act on.

Lead capture flow

Where it suits the use case, an optional step that lets users save or receive their results, connected to your CRM or email tool.

Measurement setup

Tracking for starts, completions, result types and lead submissions, so you can see how the tool is used and what it contributes.

Timeline

Typically 4–6 weeks.

The exact schedule is set in your proposal. It depends on scope, approvals and how quickly we receive access and inputs.

What we need from you

  • A subject-matter expert to define and check the underlying logic
  • Any data, rates or benchmarks the tool must use
  • Website access, or a developer who can embed the tool
  • Legal or compliance review if results could be read as advice
  1. Weeks 1–2

    Concept and model

    We define the use case, research search demand, and build the logic or scoring model with your expert’s review.

  2. Week 3

    UX and content

    We wireframe the tool, write the supporting copy and result text, and get your approval before development begins.

  3. Weeks 4–5

    Development

    We build the tool, connect lead capture where agreed, and set up event tracking for each step of the experience.

  4. Week 6

    Testing and launch

    We test calculations against known answers, check devices and accessibility, then launch and confirm tracking works.

Questions

Common questions about this project.

How is an interactive tool priced?

Each tool is quoted at a fixed price after a short scoping call. The main factors are the complexity of the logic, the number of inputs and result types, and whether the tool needs to connect to your CRM or other systems.

How do we know a tool is worth building?

We check before we build. During scoping we look at whether people search for this kind of help, what tools already exist, and whether yours can give a better or more specific answer. If an article or comparison page would serve the need just as well, we will tell you.

Who maintains the tool after launch?

You own the tool and its code. We document the logic and where any rates or assumptions are stored, so your team can update them when they change. Larger changes, such as new inputs, result types or integrations, are scoped as a separate project with written approval.

Commercial terms

A scoped project⁠—not open-ended hourly billing.

Your proposal sets out the deliverables, fixed project price and agreed labor limit. Work outside that scope requires your approval before it starts.

Scope this project