한국어
Sign in Start your free check

Done-for-you improvement work · Delivery details

What you receive for each page and form item, from issue to handoff.

The done-for-you service covers two existing pages and one existing form. Each page gets a work record like the one below, and the form gets its own linked record in the same format.

This page describes the human-delivered improvement service, which is quoted separately. It is not a sample of the AI visibility product; for that, see the sample report. The service observes answers on OpenAI and Google Gemini under its own scope; the AI visibility check itself now uses four engines, two repeats each.

Request a quote How we measure

FwdLink Work item · Page What you review

One work record for each page and form.

Page
The existing page URLConfirmed in writing in week 1, within the candidates named in the signed scope, with the reason it was chosen.
Evidence

The buyer questions behind the item, from your sales objections and FAQ first.

  • The AI answers we observed on OpenAI and Google Gemini, with the date, service and repeat of each
  • Who each answer named or linked, and whether your company was missing
  • A page check: the facts the buyer asked about that the live page does not state
The change

Up to three sections, using components your site already has, written from facts your team confirms. No claims about results.

  • Placed where a buyer reads it, such as under the headline
  • Kept in your own tone. The facts matter, not our wording
  • Facts we cannot source are asked for, not written

Linked form item (its own work record). The existing enquiry form: up to six fields, clearer validation messages, and the destination you already use. No new backend.

Approver
The person named in the scope as approver
Version
Preview v1Approval is recorded against this exact version. If it changes, it goes back for approval.
Checks
Version match, desktop, mobile, links, form receipt, eventThen the questions are observed again on one agreed date after release.

Applied only after your approver signs off this exact version.

Before and after

What a page change looks like.

Today

Proposed (preview v1)

Simplified page outlines. The wording on your page is your team’s.

What happens next

Approve, apply, test, hand over.

  1. Step 1

    Approve the version

    Your approver reviews preview v1 of the page section and the form change, and signs off that exact version. One consolidated revision round is available per item.

  2. Step 2

    Apply

    FwdLink applies only the approved version, from a recorded restore point, within the agreed scope.

  3. Step 3

    QA

    Published version matched to approved version. Desktop and mobile, links, one real test submission received at your existing destination, analytics event firing without personal data.

  4. Step 4

    Handoff

    Final URLs, change log, QA evidence and recovery information. Answers observed again on the agreed date. Business effects: not assessed unless there is enough data.

The handoff

What you keep at the end.

  • Final URLs for both pages and the form
  • A change log tied to the approved version
  • QA evidence: desktop and mobile, links, form receipt, event
  • Recovery information: restore point and how to roll back
  • Before and after answer observations, with the date, service and repeat of each

Business effects: not assessed

The handoff reports no lift in enquiries, traffic or AI mentions unless there is enough data to say more. A four-week project on two pages and one form does not usually establish one.

How we measure →

The six fields

Every work item has these.

  1. The page One existing page or form, with the reason it was chosen.
  2. Evidence The buyer question, the AI answer, and what the live page leaves out.
  3. The change Up to three sections on a page, or up to six fields on a form.
  4. Approver The person who signs off the exact version.
  5. Version What was approved is what gets applied.
  6. Checks Desktop, mobile, links, form receipt and the analytics event.

How the done-for-you pilot runs

Four weeks, counted from readiness.

  1. Week 1

    Questions and baseline

    Confirm up to 20 questions, observe answers on two dates and read the pages. Then confirm in writing the exact two pages and the form, within the signed scope, before anything is drafted.

  2. Week 2

    Drafts and preview

    Draft the page and form changes in your existing components, and prepare a preview to approve.

  3. Week 3

    Approve, apply, test

    Your approver signs off the exact version. We apply it and run the functional tests, with one consolidated revision round.

  4. Week 4

    Handoff and observation

    Confirm the published version matches, observe again on the agreed date, and hand over URLs, change log, QA evidence and recovery information.

Readiness means written scope, materials, an approver, access, a supported environment and a completed recovery rehearsal. Agreed dates move only with written agreement when a dependency is late. A human operator does this work with existing tools. It is a service, not part of the software.

Done-for-you improvement work: contact us for a quote. 4 weeks from readiness, priced in a written scope after a scope review. A human operator does this work.

Request a quote

Done-for-you improvement work

Tell us which page and form you suspect are missing something.
We will tell you whether the work fits before anything is quoted.

Request a quote

A scope review is free. The work is quoted before payment, with no online checkout.