Tangensys • Plan, deliver, measure
White-label AI search (GEO) for agencies
Add a practical AI-search workstream to your agency’s client delivery. Tangensys helps review brand information, useful source pages and observed answers, with a clear record of what was checked and what the client can improve.
An agency handover you can review
Your brand, brief and approval route.
- Agreed scopeBrief
- Useful outputDeliver
- Agency approvalReview
How this agency service works
White-label AI search support helps an agency review how a client’s information is represented in agreed search and assistant experiences. Work can include a question baseline, factual source-page improvements and repeatable observation records. Your agency owns the strategy and approvals; no delivery partner controls inclusion or recommendations by independent platforms.
- Agency briefScope and client context
- DeliveryTangensys completes the agreed work
- Agency reviewYour team checks it first
- HandoverShared with your client under your brand
Delivery your account manager can explain
An isolated answer screenshot cannot describe the whole market. Answers can vary with the question, platform, date and context. A useful engagement defines the sample and retains unfavourable or missing observations as well as favourable ones. Website changes should improve the information buyers can verify, while reporting distinguishes completed content work from changes in an external answer.
Where this support fits your agency
SEO agencies extending an existing retainer
Add a defined observation and content workstream alongside conventional search work. Use the client’s actual buyer questions and existing page map so AI visibility does not become a separate set of overlapping service pages.
Teams resolving incorrect brand information
Identify the factual error, source ownership and approved correction. Work begins with public information the client can maintain, rather than assuming that a new label or special file will control every assistant response.
Agencies needing a consistent review method
Agree platforms, question samples, markets and counting rules before comparing observations. The account manager can then explain the limits of the sample and show the underlying records.
What the agreed AI search visibility work can include
Use these areas to shape the brief. Your proposal identifies the actual outputs and who implements, approves and maintains them.
Question and experience baseline
Select representative questions connected to the client’s real audience and offer. Record the platform, context, date and relevant market for each observation. Keep the full sample, including answers that omit the brand or contain mistakes. A baseline is a defined review record rather than a universal visibility score.
Business facts and source ownership
Check the client’s name, services, delivery coverage and important claims against approved public sources. Identify which information the client owns and which requires an external correction request. The output explains what can be changed directly and what remains dependent on another publisher or platform.
Useful page and answer improvements
Develop clearer explanations where source pages leave buyers uncertain about scope, suitability or the next step. Retain context and supporting facts around short answers. The work follows the page’s real purpose; adding repetitive FAQ blocks or an AI label to every URL is not a substitute for useful information.
Technical and content coordination
Review the agreed crawlability, indexing and structured-data concerns alongside existing SEO responsibilities. Changes need a clear owner and validation route. The scope separates website work from external answer observations so a published correction is not automatically reported as a corrected response everywhere.
Observation reports and next actions
Present the agreed question set, observed answers, source references and completed work. Comparisons use a documented counting rule and equivalent samples where possible. Your agency can explain factual errors, missing source information and priorities without presenting a small test as market share or promising consistent recommendations.
Practical detail
A delivery record your agency can review
A useful handover makes the finding, action and approval easy to follow. This example is illustrative; it does not describe a client project or claim a result.
| Work stage | Illustrative record | Agency review |
|---|---|---|
| Observation | An agreed assistant answer describes a client service that the business no longer offers. | Keep the question, platform, date and recorded response. |
| Source review | The obsolete offer remains on an old public service page. | The agency confirms the current offer and approves the relevant correction. |
| Website action | Update or appropriately retire the old information and review useful internal links. | Validate the public page and record external corrections still pending. |
| Repeat review | Run the documented sample again after an agreed interval. | Record changed, unchanged and missing observations without assuming causation. |
Keep the sample and counting rules visible, verify factual changes and state the limits of external observations.
Choose the engagement that fits the workload
A defined first project
Start with a defined buyer-question sample and one source-information improvement. Agree the inputs, deliverable format and review decision before production. A small, clearly defined project gives your agency an opportunity to assess the quality of the output and the practicality of communication. It also reveals access or approval problems that should be resolved before more client accounts are added.
Recurring delivery support
Use an agreed account backlog for regular work, with capacity, priorities and reporting responsibilities made visible. Your agency decides which client requests move forward. The arrangement identifies what happens when urgent tasks compete with planned work, and how additional capacity is requested. A recurring scope should be reviewed when client requirements change.
Specialist project or overflow
Commission a specific task alongside your existing delivery team. Share previous decisions and identify where our responsibility starts and ends. The handover should fit your agency’s workflow so an outside contribution does not leave the account manager coordinating several conflicting versions. New requirements are reviewed as scope changes rather than assumed additions.
From the first brief to an accepted handover
The process gives your account manager a clear decision at each stage. Milestones and review rounds are agreed for the actual workload.
Set the account brief
Share the client’s approved facts, relevant public pages, buyer questions and the experiences to observe. We identify the starting task, missing information and delivery dependencies. Your agency confirms the client objective and scope. Discovery is useful when the current setup is uncertain; a rushed quotation should not hide unresolved access or implementation questions.
Prepare the agreed work
Production follows the approved brief and produces an observation baseline, source correction plan, agreed content changes and a comparable review record. The working record distinguishes drafts, recommendations, implemented changes and tests. Questions that affect facts, permissions or scope go to your nominated contact, keeping the client decision with the person authorised to make it.
Review and resolve feedback
Your agency checks the output against the agreed sign-off checks and consolidates comments. We resolve in-scope feedback through that review route. A new requirement, blocked dependency or changed business instruction is recorded separately so everyone can see its effect on cost, schedule and the original delivery decision.
Approve the handover and next scope
Keep the accepted version, completed-task record and outstanding items together. Keep the sample and counting rules visible, verify factual changes and state the limits of external observations. Your agency decides what is shared with the client and whether further work is appropriate. A successful initial task can support a capacity discussion; it does not automatically establish an unlimited delivery commitment.
Keep your agency in control of the client relationship
Your agency remains the client-facing decision owner. Day-to-day delivery runs through the nominated contact unless you explicitly approve another arrangement. If a client call is useful, agree the participants, roles and branding beforehand. The team should know who can make a commercial commitment and who is providing delivery information.
Before sharing client assets or access, agree confidentiality, permitted use, file ownership and any relevant contractual requirements. Use access suited to the task, with a record of who grants and removes it. The actual proposal identifies the delivery team and any partner involvement where relevant; specialist requirements should be discussed before sensitive client information is supplied.
A consistent review route protects everyone’s time. Consolidate client comments into one approved instruction, keep versions identifiable and record unresolved dependencies. These practices make it easier to retain your agency’s voice while giving the delivery team a brief it can act on.
What shapes your delivery quote
Pricing follows the work to be delivered, its complexity and the responsibilities included. For AI search visibility, share the proposed account or project, current setup and the client’s approved facts, relevant public pages, buyer questions and the experiences to observe. The quote should identify quantities or milestones, review rounds, client inputs and any work that remains with another provider.
Separate delivery charges from external costs such as media, hosting, licences, usage or specialist assets where relevant. Writing a recommendation, implementing it and maintaining it are different commitments. Your agency decides its client-facing price; our proposal makes the delivery scope clear so you can assess it against your own commercial arrangement.
Fixed response windows, ongoing capacity and urgent support are confirmed for the engagement. If the client changes the brief or a new dependency appears, we review its effect before proceeding. This keeps the account manager able to explain what is included and what needs a separate decision.
Handle revisions without losing the accepted version
For this service, consider a changed visibility question set. This is a hypothetical delivery situation, not a client result.
A service-specific decision
Keep new questions and counting rules separate from the original baseline. A larger or easier sample can change a score without demonstrating improvement. Retain raw answers and unfavourable observations.
A clear change record
Record the comment, source version and decision owner. A correction within the approved brief differs from a new deliverable. The agency should know the effect on scope and dependencies before promising the client a revised release.
A maintainable handover
Keep accepted assets or findings, test evidence and unresolved items together. Agree permitted client communication and future responsibility. A branded output is ready only when the underlying facts and task have passed the nominated review.
Free agency delivery review
Start with a clear scope and a practical next step.
Share your agency’s services, the client workload and the part of delivery you want support with. We’ll recommend a workable first engagement and provide a quote.
The initial review is free. Delivery, third-party charges and ongoing support are quoted separately.
Is AI visibility a replacement for the existing SEO plan?
It can be coordinated with the SEO plan because useful source pages and technical accessibility are shared concerns. The engagement adds specific questions and observation records where they help the client. It should not create competing page targets or imply that conventional search measurement has become unnecessary.
Can you guarantee that an assistant will recommend our client?
No. Independent platforms decide what appears and answers can vary. The deliverables we agree are the review method, useful source improvements and reporting records. Any observed recommendation is documented with its context and limits rather than sold as a permanent or universal result.
Can the output use our agency branding?
We can agree branded or unbranded output formats for the work in scope. Share your template, required sections and preferred terminology before production. Your agency reviews the accepted version before it reaches the client. Branding changes should be part of the brief rather than improvised at the final handover.
Will you communicate directly with our client?
The default route is through your nominated agency contact. Direct involvement requires explicit agreement about the purpose, participants and responsibilities. Your agency retains control of the client relationship, approvals and commercial commitments. A useful technical call does not change that ownership.
How long does delivery take, and how are revisions handled?
The proposal records milestones, review rounds and the information needed to meet them. Your agency supplies consolidated feedback. Late access, missing factual approval or a changed requirement can affect the plan; the delivery record identifies that dependency and the decision needed. We confirm a realistic timeline after reviewing the actual brief.
Can we test the arrangement with one client?
Yes. A defined first task or account gives your team a concrete output to review and a practical way to test communication. Agree its scope and sign-off checks first. Ongoing capacity and a larger client workload are discussed after that experience, rather than assumed from the first quotation.
How is the work priced?
The proposal prices the defined delivery scope, complexity, review rounds and responsibilities. External charges are identified separately where relevant. Your agency sets its own client-facing fees. Share the account setup and required outputs so the quote can distinguish advice, production, implementation and any ongoing support.
What should we share to receive a quote?
Start with the client’s approved facts, relevant public pages, buyer questions and the experiences to observe. Explain the result your agency needs to hand to the client and which tasks stay with your own team. That information helps us propose an observation baseline, source correction plan, agreed content changes and a comparable review record without leaving important approvals or implementation responsibilities unassigned.
Explore the related services
Let’s agree the right next step.
Tell us your goals and current setup. We’ll recommend a practical starting point and provide a custom quote.
Custom quote within 2 working days