1. Source
  2. Confirm
  3. Deploy
  4. Observe
  5. Update

Plans and pricing · inspectable work scope

Choose a governance cadence with fees, commitment and deliverables visible upfront.

Starter establishes a clear starting point. Professional exchanges a longer commercial commitment for more frequent updates, deeper reporting, scheduled scans and quarterly platform exploration. Both use the same formally named core-entry schedule.

Fees are billed monthly; each plan states its commitment, update cadence, reporting and named-entry scope.

Choose by entry count, languages and update frequency Where the immediate need is a first credible baseline and priority-entry view, Starter can frame the discussion. Source-supported

Choose by entry count, languages and update frequency

Both plans cover the named core entry points listed in the service schedule. Specific entry points, accounts, languages, regions and access conditions are confirmed before service begins.

Starter

HK$3,250/month

For teams with a focused entry-point set, a steady update pattern and primarily client-reported issues.

Prepare a Starter plan intent

Where the immediate need is a first credible baseline and priority-entry view, Starter can frame the discussion.

Plans

Choose the collaboration rhythm that fits

Both plans cover the same named core entry points listed in the service schedule. The main differences are commitment, update and review cadence, reporting depth, support channels and platform exploration.

Starter

HK$3,250/month

3-month commitment Committed service value HK$9,750

For teams with a focused entry-point set, a steady update pattern and primarily client-reported issues.

  • Named core entry points in the service schedule
  • Monthly update
  • Summary monthly action report
  • 2 strategy reviews per month
  • Client-reported issue handling
  • Email support
  • First response target within 1 business day
  • Scheduled platform exploration not included
Prepare a Starter plan intent

Shared core service scope

01

Monthly billing

Fees are normally invoiced monthly. Signed documents set invoice dates and payment terms.

02

Committed value is not necessarily prepaid

Committed service value states the total service value over the commitment term; it does not mean the full amount must be prepaid.

03

Third-party fees excluded

Plan prices exclude third-party platform, tool, licence, media, account and subscription fees.

04

Additional scope agreed separately

Additional entry points, paid accounts or regional platforms outside the service schedule are separately agreed and quoted.

05

The commitment is commercial

The commitment supports service scheduling and resource planning. It is not an AI training, relearning, recommendation or citation cycle.

Source-supported

Choose by entry count, languages and update frequency

Where the immediate need is a first credible baseline and priority-entry view, Starter can frame the discussion.

Where information spans several languages and entries and teams need to resolve variance regularly, Professional provides an ongoing monitoring, update and coordination rhythm.

Two working rhythms passing checkpoints toward the same enterprise fact core
One objective, two working rhythms

The plans match different rates of change and levels of review.

Source-supported

Compare across five dimensions

01

Scope

The breadth of core fields, languages, sources and named entries.

02

Governance depth

The detail of confirmation, versions, exceptions, sources and ownership mapping.

03

Deliverables

Baseline, entry schedule, variance record, deployment evidence and maintenance arrangement.

04

Support model

Starter uses email; Professional uses email and WhatsApp. The plan-specific first-response target is not a resolution-time promise.

05

Review need

Driven by business change, entry risk and ownership, not a fabricated performance metric.

Source-supported

A Named Entry Schedule makes scope inspectable

Every engagement should identify exact entries. The public site explains the method and never exposes a client schedule.

A Named Entry Schedule makes scope inspectable Every engagement should identify exact entries. The public site explains the method and never exposes a client schedule.
ItemDetail
EntryExact URL, page, directory, account or other public reference.
Ownership and accessWho controls it, whether access exists and which approval is needed.
ActionObserve, prepare, update, submit, recheck or retain as an exception.
State and limitRecord current stage, third-party condition, fee responsibility and uncontrollable factors.

A Named Entry Schedule makes scope inspectable. Every engagement should identify exact entries. The public site explains the method and never exposes a client schedule.. Entry: Exact URL, page, directory, account or other public reference.. Ownership and access: Who controls it, whether access exists and which approval is needed.. Action: Observe, prepare, update, submit, recheck or retain as an exception.. State and limit: Record current stage, third-party condition, fee responsibility and uncontrollable factors.

A Named Entry Schedule is not a claim of complete market or all-platform coverage.

Entry and fee responsibility

Applicable scope

Entry type determines access, approval and responsibility for external charges

These four categories prepare the scope. Actual work still follows named entries, account state and the approved service schedule.

Entry type determines access, approval and responsibility for external charges These four categories prepare the scope. Actual work still follows named entries, account state and the approved service schedule.
  • 01

    Owned channel

    Company website or client-controlled page

    The client approves content and provides website or supplier access. SmartRecall records deployment against approved pages and actions.

    Work evidence
    Page, permission, approver, publication state and existing supplier responsibility
    Boundary
    Existing hosting, developer or plugin costs remain under the client's own arrangements. Unnamed pages are not included automatically.
  • 02

    Public directory

    Public entry without a paid account

    Record the visible value, verification requirement and available correction route. The operator decides acceptance, display timing and future rules.

    Work evidence
    Public URL, verification state, submission method, response and recheck date
    Boundary
    Free access does not imply no verification, immediate editing or permanent availability.
  • 03

    Paid or enterprise account

    Entry involving a subscription, advertising or enterprise feature

    The client decides whether to open or retain the account and controls its contract, payment and administration. SmartRecall works only with approved access and scope.

    Work evidence
    Account owner, permission, approval, third-party charge and submission state
    Boundary
    Platform subscriptions, verification, advertising and other third-party charges are outside the SmartRecall monthly fee.
  • 04

    Other third-party entry

    Partner, regional or rule-specific platform

    Confirm whether the entry exists, why it matters, who controls it, and any regional, qualification, document or technical condition before choosing an action.

    Work evidence
    Entry rationale, applicable region, dependency, risk and separate-scope decision
    Boundary
    This does not claim cross-border capability, support for every platform or automatic coverage. Extra work is scoped first.

Entry type determines access, approval and responsibility for external charges. These four categories prepare the scope. Actual work still follows named entries, account state and the approved service schedule.. Company website or client-controlled page: The client approves content and provides website or supplier access. SmartRecall records deployment against approved pages and actions. Page, permission, approver, publication state and existing supplier responsibility Existing hosting, developer or plugin costs remain under the client's own arrangements. Unnamed pages are not included automatically.. Public entry without a paid account: Record the visible value, verification requirement and available correction route. The operator decides acceptance, display timing and future rules. Public URL, verification state, submission method, response and recheck date Free access does not imply no verification, immediate editing or permanent availability.. Entry involving a subscription, advertising or enterprise feature: The client decides whether to open or retain the account and controls its contract, payment and administration. SmartRecall works only with approved access and scope. Account owner, permission, approval, third-party charge and submission state Platform subscriptions, verification, advertising and other third-party charges are outside the SmartRecall monthly fee.. Partner, regional or rule-specific platform: Confirm whether the entry exists, why it matters, who controls it, and any regional, qualification, document or technical condition before choosing an action. Entry rationale, applicable region, dependency, risk and separate-scope decision This does not claim cross-border capability, support for every platform or automatic coverage. Extra work is scoped first.

The diagram does not name a supported-platform list and does not treat third-party charges as SmartRecall service fees.

Approval readiness

Working framework

Prepare six inputs before turning a plan into an approvable scope

Start with an accountable owner, priority facts and core entries. The remaining material can be organised as the scope becomes clear.

01

Fact owner and approver

Identify who can confirm business facts, who approves public wording and who accepts the final service scope.

02

Priority facts and known changes

Name the identity, service, price, location, contact or qualification facts that need attention, including known effective dates.

03

Draft named-entry list

Start with the most important web pages, directories, accounts, language versions or other public entries, then confirm each one.

04

Accounts, access and dependencies

Record who currently holds access, which actions require approval and where platform charges or verification may apply.

05

Languages, markets and publication limits

Confirm the languages and markets in scope, then separate publishable facts, qualified wording and non-public information.

06

Commercial, legal and review cadence

Name the procurement or contract reviewer, expected update cadence and internal response route. Formal terms still follow approved documents.

The current assessment prepares a browser-only summary. It does not transmit or store information, or create an order.

Prepare plan and approval inputs

Applicable scope

Commitment and exit principles remain under legal and commercial review

The proposed principle is to define scope, responsibility, deliverables, dependencies, third-party fees, change and exit handling in writing.

Any term, payment, renewal, termination or liability provision belongs only in an approved proposal or signed document.

This is not a published contract term.

Source-supported

Approved plan information

Starter and Professional monthly fees, commitments, cadence, reporting, reviews, support and first-response targets are listed from the current approved plans.

Exact core entries remain named in the formal service schedule. Third-party fees and extra entries, paid accounts or regional platforms are separate scope.

Plan information is available for comparison. Actual service, contract and statutory particulars follow approved documents.

12

Service deliverables

Every engagement leaves an operating record that the next owner can audit and maintain. The method is documented with it.

01

Canonical deliverableConfirmed Enterprise Fact Register

Confirmed Enterprise Fact Register

A maintained record of client-confirmed identity, service, location, policy and other core business facts, with ownership and update state.

02

Canonical deliverableEntry-Point Register

Entry-Point Register

The websites, pages, platforms, accounts, languages and regional entry points in the service schedule, with access status.

03

Canonical deliverableCross-Source Variance Register

Cross-Source Variance Register

Contradictions, omissions and stale content across sources, including the authoritative version still awaiting a decision.

04

Canonical deliverableEvidence Register

Evidence Register

Links material facts to sources, dates, applicable scope and approval records for traceability.

05

Canonical deliverableLanguage Consistency Matrix

Language Consistency Matrix

Compares Traditional Chinese, English, Simplified Chinese and any agreed language versions for semantic or currency drift.

06

Canonical deliverableOwnership and Approval Map

Ownership and Approval Map

Defines who supplies, reviews, approves and maintains each fact class and entry point.

07

Canonical deliverableInitial AUC / ATA Baseline

Initial AUC / ATA Baseline

A dated initial observation with stated scope, model and method limits; it is not a ranking, recommendation or citation guarantee.

08

Canonical deliverableUpdate Log

Update Log

Tracks each approved change, affected entry point, date, actor and result.

09

Canonical deliverableDeployment Status Record

Deployment Status Record

Separates awaiting approval, scheduled, deployed, verified and blocked items, with the next action retained.

10

Canonical deliverableMonthly Action Report

Monthly Action Report

Summarises findings, completed corrections, unresolved gaps, risks and next-period priorities.

11

Canonical deliverableCorrective Action Recommendations

Corrective Action Recommendations

Turns observed issues into recommended actions with owners, sequence and dependencies.

12

Canonical deliverableNext Review Schedule

Next Review Schedule

Confirms the next update, strategy review, approval points and client inputs required.

Fit

Who and what SmartRecall is for

SmartRecall is designed for teams that manage business facts across multiple sources over time. The starting plan is shaped by scale, update frequency and collaboration needs.

01

Who is a good fit

Business facts already span several public or controlled entry points and require ongoing coordination.

  • Hong Kong SMEs and local brandsTeams that need clear business information across multilingual sites, maps, directories and platforms.
  • Multi-service or multi-location teamsService names, credentials, locations, opening details or policies can diverge between sources.
  • Evidence- and approval-conscious sectorsTeams that need facts, sources, ownership and approval paths kept distinct.
  • Lean marketing or operations teamsOrganisations without a dedicated owner for continuous cross-platform fact inventory, correction and verification.
02

Common data problems

Most organisations already have plenty of content. The problem is that each source may tell a different version.

  • Identity mismatchCompany name, brand, address, contact or opening information differs between sources.
  • Service ambiguityAudience, service scope, limits or differentiation are not expressed clearly.
  • Stale contentDiscontinued services, old policies or former locations remain discoverable.
  • Language driftLanguage versions are updated at different times, creating gaps in promises, details or limits.
  • Unclear ownership and approvalThe team sees a problem but does not know who decides, approves and completes the correction.
03

Starter is a better fit when

A basic governance rhythm is needed and the volume of change and monitoring remains manageable.

  • The core entry-point set is focusedPrimary entry points can be clearly named in the service schedule, with limited extra-platform demand.
  • A monthly rhythm is sufficientBusiness facts do not change frequently and monthly normalisation and correction fits operations.
  • Issues are mainly reported by the clientThe team can flag emerging issues for SmartRecall to follow up.
04

Professional is a better fit when

Information changes frequently across several entries and requires scheduled checks plus ongoing cross-team coordination.

  • Facts change more frequentlyServices, locations, policies or entry points change often enough to need a fortnightly rhythm.
  • A scheduled scan is neededThe team wants a monthly proactive review of agreed scope in addition to client reports.
  • Cross-team coordination is heavierDetailed reporting, more strategy reviews and WhatsApp support are useful.
  • Platform exploration mattersThe team wants a quarterly view of emerging entry points or platform changes and their fact-layer implications.

08

Observable measurement

Track improvement through records, variances and completion states. Each measure states its method, date, scope and reviewable evidence.

Each dimension states its definition, observation method, applicable conditions and reviewable evidence.

01

Identity Accuracy

Identity Accuracy

Observe whether names, addresses, contact details and other core identity facts agree with the approved register.

Observed through
Observed through entry-point checks, variance records and evidence links.
Measurement conditions
Scope: in-scope, verifiable sources.
02

Service Understanding

Service Understanding

Observe whether public material clearly conveys audience, service, limits and differentiation.

Observed through
Observed through content mapping, question tests and human review.
Measurement conditions
Observation conditions: query, model, time and source.
03

Cross-Platform Consistency

Cross-Platform Consistency

Observe whether the same business facts agree across the contracted entry points.

Observed through
Observed through the Cross-Source Variance Register and deployment verification.
Measurement conditions
Platform state: approval and display timing are recorded separately.
04

Evidence Coverage

Evidence Coverage

Observe whether material business facts have traceable sources, dates, scope and approval records.

Observed through
Observed through complete and missing states in the Evidence Register.
Measurement conditions
Evidence use: connect statements to sources and record platform adoption separately.
05

Information Currency

Information Currency

Observe whether known changes enter the update, deployment and verification flow for agreed entry points.

Observed through
Observed through update dates, deployment states and incomplete dependencies.
Measurement conditions
Refresh timing: recheck against the platform's public state.
06

Answer Variance

Answer Variance

Observe factual differences between relevant outputs under a stated question, time, model and method.

Observed through
Observed through reproducible test records and variance classification.
Measurement conditions
Observation unit: stated query, model, date and source.
07

Completed Corrections

Completed Corrections

Observe whether approved corrections complete deployment and the required verification.

Observed through
Observed through the Update Log and Deployment Status Record.
Measurement conditions
Completion: agreed work and required verification are complete; platform state is recorded separately.
08

Outstanding Gaps

Outstanding Gaps

Observe items still awaiting data, approval, access, third-party action or further decisions.

Observed through
Observed through variance records, blocker reasons and named next owners.
Measurement conditions
Gap state: list the remaining items and next action.

FAQ

Frequently asked questions

Direct answers on fees, service scope, data handling and delivery arrangements.

01How is SmartRecall different from SEO or GEO?

SEO commonly focuses on search visibility, while GEO is often used for optimisation related to generative engines. SmartRecall's core is the enterprise fact layer: organising, confirming, deploying and maintaining business facts across sources. This can support other strategies but does not replace full SEO, content, advertising or public-relations services.

02How are visible changes in search and AI platforms recorded?

SmartRecall records the question, date, entry point and visible output. Search and AI platforms process public information through their own models, indexes and policies, so reports separate completed work from platform state.

03Why is Professional's monthly fee lower?

Professional uses a longer nine-month commercial commitment, giving SmartRecall more predictable scheduling and resource planning. The plan also includes more frequent updates, reports, reviews, scanning and support.

04How is billing handled, and must committed value be prepaid?

Fees are normally invoiced monthly. Committed service value is the total service value across the term and does not mean the full amount must be prepaid. Signed documents set invoice dates and payment terms.

05How are third-party platform fees handled?

The relevant supplier charges platform, tool, licence, account, media or subscription fees separately. The plan confirmation identifies each responsibility and arrangement.

06Can extra entry points, paid accounts or regional platforms be added?

They can be assessed. Entry points, paid accounts or regional platforms outside the service schedule are separately agreed and quoted based on access, language, effort and third-party conditions.

07How is search or AI status recorded after an update?

SmartRecall records the deployment date and rechecks the visible state under the agreed scenario. The relevant platform handles crawling, indexing, caching, model refresh and answer generation on its own schedule, and the report shows those states separately.

08What client data is required?

Only business facts, sources, approvals, entry points and access needed for the agreed service should be provided. Data minimisation, permission scope, transfer method and retention must be confirmed before formal mobilisation.

09What happens to data when service ends?

Handover, export, deletion, retention and legal exceptions are governed by the formal agreement and privacy notice. SmartRecall will not invent a fixed period or commitment on the website before approval.

10What can ATA do, and what are its limits?

ATA is a proposed proprietary operating and observation framework for registering baselines, comparing variance, retaining observations and planning corrections. It can support reproducible tests, but cannot control third-party models, indexes, recommendations, citations or output stability.

11What does the service deliver?

The engagement produces usable operating records for enterprise facts, entry points, variances, evidence, language consistency, approvals, baselines, updates, deployment, action reporting, corrective recommendations and the next review. Exact scope follows the service schedule.

30

The first 30 days

This is the standard mobilisation rhythm. The final order depends on data availability, approval speed and the agreed service schedule.

  1. Day 1–7

    Set scope and build the inventory

    Work

    • Confirm the service schedule, languages, regions and named core entry points
    • Inventory current business facts, sources, accounts and known issues
    • Map initial owners, approvers and access dependencies

    Client input

    • Provide authoritative documents, current pages and account information
    • Name fact owners, approvers and the primary contact

    Outputs

    • Draft Entry-Point Register
    • Evidence inventory
    • Draft Ownership and Approval Map
  2. Day 8–14

    Confirm facts and establish the baseline

    Work

    • Normalise core business facts and compare sources
    • Review language versions and evidence coverage
    • Establish initial observations with stated scope and method limits

    Client input

    • Resolve conflicting source material
    • Approve authoritative wording and priorities

    Outputs

    • Confirmed Enterprise Fact Register
    • Cross-Source Variance Register and Language Consistency Matrix
    • Initial AUC / ATA Baseline
  3. Day 15–21

    Prepare, approve and deploy corrections

    Work

    • Convert confirmed variances into corrective items
    • Prepare or execute approved updates according to access permissions
    • Record blockers and third-party dependencies

    Client input

    • Approve changes within the agreed window
    • Provide required account access or arrange an internal implementer

    Outputs

    • Corrective Action Recommendations
    • Update Log
    • Deployment Status Record
  4. Day 22–30

    Verify, report and schedule the next cycle

    Work

    • Verify observable deployment states and remaining gaps
    • Sample relevant outputs and variances under the agreed method
    • Compile completed work, risks and next actions

    Client input

    • Join the strategy review and confirm priorities
    • Confirm the next update and approval window

    Outputs

    • Monthly Action Report
    • Outstanding-gap list
    • Next Review Schedule

The sequence follows data completeness, access, approvals and platform processing. Each review records the date and next action.

Preparing the next step

Choose a plan and prepare a summary you can keep.

Compare the plans, prepare what you need, then continue through any of the formal channels below.

Confirm the facts, entries and owners, then turn the plan into an approvable service scope.

The initial assessment prepares a Starter, Professional or comparison intent locally. Once an official channel is approved, you decide whether to send it.