RankMore AI

Engagements & pricing

Know the scope.
Know what
done means.

A clear question, a defined change or work that continues. Compare the ways we could work together, and what each proposal needs to make clear.

Explore the three models
Scope before commitment.Compare inputs, outputs & ownership

Three ways
to move the work on.

Explore what each model could cover. These are examples to discuss, not packages ready to buy or an automated assessment of your business.

A different starting point,
not a higher tier.

Diagnosis need not lead to implementation. A defined project need not become ongoing work. Agree only the work you need.

See the full comparison
Example scope / for discussion01

Defined review

Diagnosis

Resolve one agreed question using a fixed set of evidence.

Question
What is making the journey from a service page to contact unclear?
Inputs
Agreed pages, the intended customer journey and available analytics, with their limits recorded.
Deliverables
A findings record, supporting evidence, priorities and a recommendation for the next decision.
Ownership
We review and explain. Your team supplies context and confirms the question and evidence set.
Done means
The agreed question is addressed, findings are traceable and recommendations are reviewed with you.
Not included
Implementing changes, a full-site audit or ongoing monitoring unless separately agreed.

Price pending approval.
Agree the evidence set and deliverables before starting.

Discuss diagnosis
Example scope / for discussion02

Scoped project

Focused
implementation

Turn an approved set of priorities into completed, checked work.

Change
Clarify an agreed service page and its route to the contact page.
Inputs
Approved brief, page list, relevant access, existing content and the people responsible for review.
Deliverables
Agreed page changes, a change record, completion checks and a handover with remaining issues.
Ownership
The proposal assigns each build, content, review and release step to us, your team or an agreed third party.
Done means
Named deliverables pass agreed checks. The designated approver accepts the work before release.
Not included
A full website rebuild, extra pages or additional revisions outside the approved scope.

Quote after a fit check.
Price, milestones and change process need approval.

Discuss implementation
Example scope / for discussion03

Recurring work

Ongoing work

Maintain an agreed queue of improvements once the starting position is clear.

Focus
Review search and page evidence, then prioritise the next agreed improvements.
Inputs
A stable baseline, relevant access, current priorities and a named person who can approve work.
Deliverables
An evidence-led work queue, agreed recurring capacity, completed work records and regular reporting.
Ownership
We manage the agreed work and explain progress. Your team confirms priorities and handles its assigned dependencies.
Done means
Each work cycle is checked against its scope, then reviewed before the next priorities are agreed.
Not included
Unlimited tasks, guaranteed rankings or automatic expansion into other services.

Price and minimum term pending approval.
Capacity, review dates and stop points need agreement.

Discuss ongoing work

Illustrative scope documents, not client work, quotations or promises of results. Selecting a model only changes this example.

Compare the commitment.

The important difference is the responsibility you are asking us to take on.

To agree
Diagnosis
Focused implementation
Ongoing work

Starting point

A bounded question; the cause or next step is uncertain.
The required change is understood and can be scoped.
A stable baseline and a continuing need for improvements.

What you provide

Context, a clear question and an agreed evidence set.
Approved requirements, relevant access and timely decisions.
Access, business priorities and a regular review contact.

What you receive

Findings, evidence, recommendations and a decision record.
Named changes, checks and a handover record.
Agreed capacity, a prioritised queue, delivery records and reporting.

Who owns what

We own the review. You decide what happens next.
Every task, dependency and approval has an agreed owner.
We own the agreed work queue. Priorities are reviewed together.

Where it stops

At the agreed findings and recommendation. Changes are separate.
At acceptance of the defined work. Additions need approval.
At agreed review or stop points, under the approved terms.

Commercial status

Price pending owner approval.
Quote after fit and scope review; terms pending approval.
Price, capacity and minimum term pending owner approval.
Next step
Discuss diagnosis
Discuss implementation
Discuss ongoing work

What changes the price

Four things
shape the scope.

The number of deliverables is only part of the work. These factors change the research, coordination and checks a proposal needs to cover.

01Current state
Platform age, site size, access, data quality and previous work determine what needs to be untangled first.
02Market
Languages, locations, relevant regulation, buying cycles and competition change the research and review needed.
03Responsibility
Advice, implementation, content production and coordination with your team or other suppliers involve different work.
04Risk
Migrations, live sales, customer data and critical automations can require additional testing, permissions and a way to undo changes.

Before you say yes,
put it in writing.

A proposal should make a decision possible. The examples above do not replace a written scope or approved commercial terms.

What the proposal must define

  • The question or change, named deliverables and what is excluded.
  • The access, evidence and information your team must provide.
  • Who implements, coordinates, reviews and approves each step.
  • The order of work, dependencies, milestones and timing.
  • The checks used to accept each deliverable and approve release.
  • The full price, payment terms and any recurring capacity or minimum term.
  • How delays, scope changes, revisions and cancellation are handled.
  • Reporting intervals, review dates and clear stop points for recurring work.

From question to decision

  1. 01

    State the problem

    Start with your website, market and the decision you need to make.

  2. 02

    Check the fit

    Discuss the smallest useful scope and the information needed to price it.

  3. 03

    Agree the boundaries

    Review the written scope, exclusions, responsibilities, timing and price.

  4. 04

    Proceed or walk away

    Decide after seeing the terms. Payment and implementation must wait for explicit agreement.

This preview does not take payment or send an enquiry. The contact page is the next step for exploring a brief.

Pricing questions

The terms
behind the work.

Why are prices not visible yet?

The catalogue is still under review. Prices and terms are pending owner approval, and public purchasing is not available in this preview. A price should be published only when the scope, onboarding, delivery checks and commercial terms are ready.

Will you offer fixed-price services?

Fixed-price work is planned where the inputs, boundaries and completion checks can be repeated reliably. This page does not offer an approved fixed-price package. Work with significant unknowns may need a separately priced diagnosis or an agreed custom scope first.

Do you require a long contract?

A long contract is not the default in the proposed model. No minimum term or cancellation policy is approved here. Any ongoing proposal must state its term, review points and cancellation rules before you commit.

Can we start with a smaller piece of work?

That is the intention when a smaller scope can answer an important question or establish a useful baseline. Diagnosis can stand alone. Any later implementation or ongoing work would need its own approval.

What happens if the scope changes?

The proposal must explain how changes, revisions and delays are handled. Added work should have an agreed owner, revised timing and any price change approved before it starts. No revision allowance is set by this preview.

Can our team handle the implementation?

The scope can separate our review and recommendations from your team's build work. Each task, handover and approval needs a named owner, including any third-party dependencies.

What access or information should we share?

Start with a public website address, market and a plain-English description of the problem. Do not include passwords, private customer data or access keys. Any required permissions and data handling arrangements must be agreed for the actual scope.

Start with one useful decision

What needs
to change?

You do not need a technical brief. Start with the situation, the decision you need to make and who will be involved.

Discuss scope & pricing

Opens the contact page. No purchase or commitment.