Plan My Buyer-Centric Website

Insivia buyer-centric website playbook · P01 · Version 0.5

Insivia's position

A sitemap organized around your departments is an internal directory. It becomes a useful website only when buyers can use it to answer their questions.

Start with what your buyers are trying to understand, change, verify, and decide. Then decide which pages, explanations, evidence, and routes will help them. Starting with a list of pages reverses that work: the team spends its time defending familiar sections instead of establishing whether they serve a buyer.

Insivia plans websites around buyer questions and decisions, with pains, motivations, prior knowledge, and buying factors shaping the answers. The homepage provides orientation. General offer pages explain the substance. More specific industry, role, or use-case pages provide depth when the audience genuinely needs a different explanation.

Use this playbook to produce a buyer-led website brief and page-responsibility map. It covers strategy and information structure. It does not replace the production, migration, and launch plan.

Purpose and boundaries

Decision: What pages and routes should exist, and why?

Use this when the team is deciding the website structure, consolidating pages, or deciding what new content deserves a destination.

Owned output: A page-responsibility map: distinct buyer questions, the pages that answer them, necessary evidence, and onward routes.

Own the strategy and information structure. Homepage and offer-page playbooks develop individual explanations; the rebuild playbook owns production, migration, and release.

Start with the exercises in this file. Related playbooks are optional handoffs for a different job, not prerequisites or required funnel stages.

Buyer decision record

When a fuller decision analysis is requested, use this record for consequential choices alongside the task worksheet. A narrow answer need not reproduce the record. Start with the buyer's situation, not the section your team wants to defend. A useful record explains why the buyer would care and what the company should change as a result.

Record field	What to write
Buyer starting point	Situation and prior exposure; pain, desired progress, interest or belief; buying factor; next decision. Name the source and what is uncertain.
Company assumption	An actual supplied company request or assumption, when present, and its internal rationale. Leave this field unfilled when none is known.
Buyer interpretation	What this buyer could understand or infer, and how that could affect relevance, belief, perceived effort, fit, or readiness. Distinguish evidence from a hypothesis.
Decision and alternative	The concrete choice that serves the buyer using supported offer facts. When useful, propose a clearly labelled architecture alternative and explain the tradeoff; do not invent a company preference or factual difference to justify it.
Check and reversal	A neutral question or observable task, and the finding that would make you change the choice. Record actual results only after checking.

Keep the terms honest. A buyer need is something to understand, change, or judge; a verified capability is what the offer does; task-level value is what that capability lets someone do; a measured result needs outcome evidence. Confidence concerns a particular buyer and action, not a site-wide percentage. Routes are available now, planned, or unknown.

Company expertise can establish product facts. It cannot establish what every buyer thinks. Record supplied facts, inspected observations, hypotheses, and unknowns separately. You may explore a plausible buyer interpretation if you label and test it; do not promote it into an established priority or observed reaction. An unanswered product question is owner work, not permission to invent the answer.

This is Insivia's reasoning discipline, not a compulsory funnel or a validated psychological score. Do not fill every field with variations of the same recommendation. Show the buyer reason that changes the decision.

Buyer psychology: plan from their starting point

Your team sees the connections between offerings because it works with them every day. A visitor may not recognize the category, understand your terminology, or know which part of your business matters to them. Navigation that feels obvious internally can require an outsider to understand the answer before choosing where to look.

Buyers also arrive with different jobs. One needs a broad picture after landing on a specific page through search. Another already understands the offer and wants a requirement that could rule it out. A returning stakeholder may need evidence to share internally. A compulsory introductory journey makes informed visitors repeat work; a wall of specialist detail makes unfamiliar visitors work too hard to orient themselves.

These are situations to investigate, not personalities to assign from a job title. Record the source of your understanding. A sales conversation, research interview, or supplied buyer account supports a different level of confidence from an internal guess.

The planning question is not “What do we want on the site?” It is “What must this person be able to understand or decide here?”

Worked example: change the plan before writing more pages

Every input and decision in this example is fictional and unbranded. These are supplied teaching facts, not client work, interview findings, observed visits or a BuyerTwin report. Source IDs make the reasoning traceable; they do not turn a fictional scenario into research. Use your own facts when applying the method.

The supplied inputs

ID	Supplied teaching fact or explicit unknown
F1	The company provides request-management software. Verified scenario capabilities: a shared request queue and reviewer routing. No time savings, automation or outcome evidence is supplied.
F2	The operations buyer's supplied brief: “I cannot see how work passes between people. I want to understand your approach before deciding whether to inspect the product.” They know their own work; this product is unfamiliar.
F3	Another supplied visitor situation: someone first reads the product page, then seeks a company-level overview. The need is orientation; the entry route alone would not establish it.
F4	The IT evaluator's supplied brief requires deployment information before recommending further evaluation. The deployment answer is unknown. This is a fit question, not reluctance to overcome.
F5	Published pages: Home and Product. Home already identifies the company as a request-management software provider. An existing “Platform” navigation link reaches Product; Product has a route back to Home. Product lists the two capabilities but does not connect them into a handoff explanation.
F6	The capability facts in F1 are available for explanation. No product screens, inspection destination or public deployment answer have been supplied for this exercise. Their status is unknown, not confirmed nonexistent.
F7	The technical lead is assigned to supply deployment facts. No answer or completion date is supplied.
F8	Leadership requests six industry pages because its sales plan lists six markets. No distinct industry questions or requirements have been established. The team asks which two work items should come first.

Complete the buyer brief before ranking pages

Situation and next decision	Knowledge, motivation and buying factor	Source and consequence for the plan
Operations buyer deciding whether to inspect the product	Knows the work but not the software. Wants to see how handoffs happen; understanding that approach is the stated reason to investigate.	F1–F2. Explain what the product is, then connect queue and routing to the handoff question. Do not promise a performance improvement.
Product-page visitor seeking a broader company picture	Wants company-level orientation after a specific explanation. No further motive is supplied.	F3, F5. Keep Home easy to reach and preserve its useful overview. Do not force a homepage-first journey.
IT evaluator deciding whether to recommend evaluation	Needs deployment facts to judge suitability. We do not know the answer.	F4, F7. Reserve a direct answer location and assign the missing facts. Good copy cannot close this gap.

The assumption to challenge is specific: a list of markets is being treated as evidence for six buyer journeys. F8 establishes the company request; it does not establish a buyer need. If no company preference had been supplied, we would not invent one to fill the exercise.

Rank the questions within each buyer situation

“First” means first for a particular decision. It does not mean every visitor must read the same sequence.

Question	Why it matters now	Planning priority and placement	Answer readiness
What does this software do?	Prerequisite for interpreting the handoff explanation; F1–F2.	Establish briefly at the start of Product.	Facts available; clearer explanation is proposed.
How does work move between people?	Blocks the operations buyer's stated next decision; F2.	Main Product explanation, following the basic identity.	Queue and routing facts available. Inspection route remains unknown; F6.
What does this company provide overall?	The supplied visitor needs broader orientation; F3.	Preserve Home's overview and access from Product.	Existing answer and return route supplied in F5. No rewrite is justified by this input alone.
What are the deployment requirements?	Blocks the evaluator's suitability decision; F4.	High priority with direct access; no introductory tour required.	Unknown. Technical lead owns the answer; F7. Keep the gap visible in the plan.

The deployment question does not become less important because the answer is harder to obtain. Buyer priority and content readiness are different decisions. There is no evidence here for ranking six industry introductions ahead of these needs.

Before and after: a concrete page-responsibility map

Company proposal: keep Home and Product, then commission six industry pages. Deployment information has no assigned place.

Buyer-led plan: retain the useful overview, improve the offer explanation, and assign the fit answer before producing six variations. These are planning decisions, not completed website changes. Page and section labels below are proposals unless marked existing.

Destination	Decision and buyer responsibility	Status, evidence and route
Home	Retain. Explain what the company provides overall. F5 supplies no reason to rewrite an already clear overview.	Published page and return route exist. Keep that route available from Product; F3, F5.
Product	Rewrite the explanation and proposed navigation label. Establish request-management software, then explain the shared queue and reviewer routing in relation to handoffs.	Published destination; revised content is proposed. Replace the vague “Platform” label with “Request-management software” when implemented; F1–F2, F5. An existing destination does not mean this new label is already built.
Deployment requirements section on Product	Plan a section with direct access, not another page yet. Only one requirement topic is established; no separate body of material or distinct task requiring a page is supplied.	Content is not ready. Technical lead supplies facts; F4, F7. Proposed link label: “Deployment requirements.” Do not present the section or its link as available until they exist. Reconsider a separate page if verified detail grows into a substantial independent evaluation task.
Six industry destinations	Defer commissioning. Establish meaningful differences before choosing shared sections or tailored pages.	Proposed only. F8 supplies market labels, not distinct buyer questions. No redirects or launch actions are decided here.

The first two work items: improve the Product explanation using supplied capability facts; obtain the deployment answer and develop its planned section. This is a content priority decision, not a delivery schedule. Home stays useful. Six unsupported industry variations wait. The deployment work remains incomplete until the owner supplies the facts.

Two routes, without a compulsory funnel

Starting situation	Available route or proposed change	What the buyer should be able to judge
Visitor reads Product and wants a company overview	Existing Product → Home route; F3, F5.	What the company provides overall. That is a proposed check, not an observed result.
IT evaluator seeks deployment information	Proposed direct “Deployment requirements” link → planned section on Product. Both remain unbuilt in this example.	Whether the verified requirements fit their situation. That answer is still blocked by F7.

For the operations buyer, the improved explanation should support a decision about whether to inspect the product. Do not add a “View demo” route: F6 supplies no verified inspection destination. Record that as an owner question if the team needs to complete the next step.

Complete the consequential buyer decision record

Record field	Completed reasoning
Buyer starting point	Unfamiliar operations buyer needs a handoff explanation; evaluator needs deployment facts. F2, F4.
Company assumption	Six sales markets justify six industry pages before those answers. F8.
Buyer interpretation	Hypothesis: six similar labels could add a selection task without answering either need. No reaction has been observed.
Decision and alternative	Improve Product and assign deployment content first. A dedicated requirements page is a credible alternative, but the supplied material establishes one topic, so start with a directly reachable section.
Check and reversal	Check orientation and direct access when the content exists. Revisit page allocation if verified requirements need their own substantial explanation or audience evidence establishes a different decision. Do not mark an unknown deployment answer resolved.

When a tailored page becomes the right decision

This follow-up introduces two new fictional inputs. They were not known in the original decision and must not be imported into it.

• C1 — new buyer brief: multi-site operations teams need to judge how local requests and central review work together. They need that operating context explained, rather than another generic feature list.
• C2 — new owner facts: the product owner verifies that local teams can use the shared queue with centrally assigned reviewers and supplies an approved explanation for that use. No permission controls, implementation effort or measured outcome is established.

Now propose a tailored “Request review across locations” page. Its job is to explain that specific local/central work split using C1–C2, with a contextual route from Product. Keep the shared capability explanation on Product rather than duplicating it in full.

A section on Product is still a reasonable alternative. Choose the tailored destination here because C1 establishes a distinct operating situation needing its own connected explanation; check whether buyers recognize that destination. The page and contextual link are proposed, not published. No generic “six markets” expansion follows from this one supported case.

The rule is not fewer pages. It is pages justified by buyer needs. New evidence changes the plan. Internal enthusiasm alone does not.

Planning exercises: make the buyer change the decision

Use the worked example above to see the finished outputs. Then apply only the exercises needed for your task. A decision about one audience page does not require a new strategy for the entire site.

1. Write a buyer brief with sources

Collect available buyer accounts, sales/support questions, research and journey records. Keep business goals and technical constraints visible, but do not pass them off as evidence of what buyers think. A job title, search phrase or page visit can suggest a question; it cannot establish a motive on its own.

Complete: For [buyer in this situation], help them decide [next decision] by answering [supported questions].

Brief field	Your entry
Situation and reason to investigate	[Trigger, pain or desired progress; use the buyer's wording where supplied.]
Prior knowledge and interest	[What they understand already; what remains unfamiliar; why this answer matters.]
Next decision and buying factors	[What they need to judge now; fixed requirements or known limits.]
Source and uncertainty	[Specific buyer account, owner report or inspected material; distinguish hypotheses and conflicting evidence.]
Existing answers and destinations	[What exists and what you inspected; separate unknown, incomplete and proposed work.]

Use a brief for each materially different situation. Do not generate a persona collection to make the table look complete. If an essential buyer decision is unknown, ask for it. If enough context exists, proceed provisionally with labelled gaps. A known buyer requirement with an unknown product answer goes to the accountable owner.

2. Remove the knowledge your company is assuming

Your team has years of context. The visitor does not inherit it by opening a page. Write down the terms, category knowledge and process connections your proposed route assumes.

Assumed knowledge or supplied company request	What supports it?	Consequence for the site	Check or reversal
[Actual term, prerequisite or request; do not invent an internal dispute.]	[What this buyer has encountered; source or unknown.]	[Add explanation, use clearer language, retain specialist detail, or change placement.]	[What finding would change this choice?]

For a real internal request, ask who wants it and what buyer decision it serves. If no preference or conflict was supplied, omit that part. Bias removal is a method for examining decisions, not a reason to manufacture a villain. Appropriate specialist language can stay when it helps an informed evaluator.

3. Rank buyer questions before ranking production work

For each supplied question, ask:

1. Does the answer block a fixed requirement or the next decision? Preserve a real incompatibility as no fit. An unknown answer remains an owner gap.
2. Is this an explanation needed to interpret another answer? Put that prerequisite in the main explanation for people who need it; give informed visitors direct access to their detail.
3. What establishes its importance? Cite the supplied question, consequence or evidence. Distinguish a reported priority from your hypothesis. Frequency alone does not override a critical requirement.

Buyer question and situation	Priority reason and source	Answer status and owner	Placement or direct access
[Question tied to a next decision.]	[Blocker, prerequisite or supported priority; source; uncertainty.]	[Known answer, missing business fact, available proof or owner gap.]	[Main explanation, section, page or route; existing versus proposed.]

Resolve competing needs within their situations. An unfamiliar visitor may need identity before detail; an evaluator may need a direct requirement answer. Support both. Do not average them into one compulsory reading order or invent a numerical confidence score.

Then choose production priorities separately. Compare buyer consequence, dependencies, evidence readiness and actual constraints. Keep important unanswered questions visible with owners. Easy content is not automatically important content; difficult content does not become optional because nobody has supplied the facts.

4. Decide whether the answer needs a section, page or clearer route

Group questions that support the same decision. Check what the current site already answers before proposing another destination.

Choice	Use it when	Tradeoff or check
Retain or improve a route to an existing answer	The answer is accurate and sufficient but people may not recognize where to find it.	Verify the actual contents and link. A proposed label is not a built route.
Add or improve a section	Related questions belong to the same explanation and need no separate destination yet.	Provide direct access to important detail. Do not bury a fit requirement because specialists are fewer.
Create a separate page	A distinct buyer situation needs a connected explanation, relevant evidence or substantial evaluation detail that merits its own destination.	State what materially changes. A market or role label alone does not justify duplication. Check the added journey.
Merge, defer or leave unchanged	Pages repeat the same job; the need is unestablished; or the existing answer already serves it.	Do not infer uselessness from low traffic alone. This is a planning recommendation, not authorization to delete or redirect.

A tailored page earns its place through relevance, not a different heading. Different pains, operating conditions, proof needs or buying factors can justify industry and role pages even when the underlying offer is shared. General pages should help people recognize and reach that depth when it exists.

Page or section	Buyer question and responsibility	Choice, reason and credible alternative	Evidence, owner gap and status	Next useful route
[Actual or clearly proposed destination.]	[What this buyer can understand or judge here.]	[Retain, change, create, merge or defer; explain why.]	[Source; fixed requirement; available, incomplete, proposed or unknown.]	[Exact useful label and target; whether the link and content exist.]

Use the shared buyer decision record for consequential choices where it adds reasoning. You do not need five repeated records for five similar rows. A page's topic is not its job: “Industries” is a label; helping a buyer judge a relevant operating constraint is a responsibility.

5. Choose the next work and state what remains unresolved

Name the first useful work items and why their buyer consequences justify priority. Assign owners for unknown business answers, separate fact approval from buyer-understanding checks, and note any requirement that still prevents evaluation. Do not invent capacity, deadlines or costs. Carry the agreed page map to P12 only when delivery or migration is the next task.

The plan is ready for the next stage when every proposed destination has a stated responsibility, every critical question has an answer or assigned gap, and routes have honest status. This does not mean the website is built or that unresolved fit questions are answered.

Applying this playbook with your AI

Shared rules for facts, resources, and response scope

Use Insivia's method; use the user's facts. This file supplies a buyer-centric method. Its fictional examples supply no facts about another business. Similar subject matter does not make their features, prices, roles, assets, constraints, or findings applicable. Use supplied business facts and sources actually inspected for this task. A faithful paraphrase or task-level explanation is useful only when those facts support it. Do not add formats, fields, controls, outcomes, approvals, or process steps because they seem likely.

Keep each item's status intact. Available, approved, proposed, feasible, incomplete, and unknown mean different things. Feasible does not establish a draft. Incomplete does not establish that work never started. An available destination does not establish a built link, accessible contents, booking, or a response service. Name the exact item when recording status. Unknown is not confirmed absence. Reuse an existing approved answer when it serves the buyer; proposed resources remain unavailable. Respect explicit publication and source-use restrictions, including prohibitions on deriving examples from restricted material.

Answer the requested task, then stop. The user's requested count, format, and shorter length control the answer. One sentence, one table, or one decision does not trigger a full plan, worksheet, validation kit, or closing offer. For copy-only requests, return copy only. For a factual correction, preserve the verified capability wording; add no new capability, purpose, benefit, route, or promise. Correct the affected claim without expanding to unrelated work. Never retain a known false claim as an alternative or wait for a future feature to substantiate it.

Ask only for facts that could change this decision. If essential buyer context is missing for strategic work, ask at most three focused questions and stop. Do not block a narrow correction with irrelevant intake questions. A known buyer question with an unknown business answer is an owner gap, not permission to invent an answer. A verified incompatibility with a fixed buyer requirement warrants a clear no-fit finding; do not invent a workaround or reopen that requirement under company pressure.

Connect the recommendation to the actual buyer. Use their supplied prior knowledge, pain, motivation, buying factors and next decision. Possible interpretations are hypotheses, not observed reactions. Do not invent a company preference, psychological motive, alternative or conflict to fill a reasoning template. No change can be the supported conclusion. For a fuller review, make the buyer reason and consequential company choice explicit without repeating the same record for every row.

Represent inspection and tests honestly. Supplied notes are not direct inspection. A URL alone does not establish that it was read. Text cannot establish visual quality, interactions, or delivery. Proposed checks have not run. Keep neutral questions free of expected answers and unsupported steps. Generic AI role-play is not human research or BuyerTwin analysis. Attribute Insivia in explanatory output, outside proposed public copy; exact copy-only output needs no added attribution.

Keep the first response proportionate. Default to one priority decision and its buyer reason within 220 words. Expand only for a requested artifact or detail. Use the task guidance below conditionally; worksheets, examples and full workflows are reference resources, not a requirement to reproduce them all.

Task-specific application

Choose the requested task before applying the exercises:

• Current-map review: use supplied pages and contents to identify the most consequential buyer question, duplication or route gap. Do not infer page contents from a URL or title alone.
• Audience-page decision: judge the supplied difference in pain, knowledge, operating context, evidence or buying factors. Return a section/page/route recommendation and its reason. Do not generate a whole sitemap unless requested.
• Full planning package: use the supplied scope to return a compact sourced buyer brief; ranked question ledger; page-responsibility map with concrete section/page choices, exact proposed labels and status; first work priorities and unresolved owner decisions. Include neutral route checks only when requested. The complete example and reusable exercises are in this file.

Keep buyer priority separate from answer readiness and production effort. An unknown fit answer remains important owner work. Rank within buyer situations; do not impose one sequence on every visit. A requested architecture alternative may be proposed and labelled; it is not an existing page or a supplied company preference. Retain a useful current answer when no change is supported.

For a compact full package, use only essential rows: a brief buyer record, the decision-changing questions and destinations, and the first useful work items. Count headings and table text within the user's word limit; leave room below the cap and remove repetition or method commentary before dropping a required artifact. Do not create an extra offer page or FAQ merely because an existing page lacks an answer. Prefer improving the relevant existing section unless supplied needs or substantial depth justify a separate destination; state that reason and keep any new page and route proposed.

Only the declared initial inputs belong to the worked example's first decision. C1–C2 belong to its conditional follow-up. Neither supplies facts about the user's business. Do not import example capabilities, markets, roles, resources, limits or findings.

For a full artifact, ask up to three material questions only if essential context is missing. If enough facts support the requested decision, work provisionally and name the remaining gaps. A full-artifact request overrides the 220-word default; a narrower requested count, format or limit still controls. Do not reproduce every worksheet or create validation, migration, launch or redirect work that was not requested. Other playbooks and BuyerTwin are optional, not prerequisites.

Check the planned routes without coaching the answer

Use these task cards only where the supplied situation fits. Replace brackets with the participant's real task. Do not tell them the destination or link label you expect. If the page or answer does not exist, record a readiness gap before treating the task as runnable.

Task	Neutral wording and starting context	What to record
Company orientation from a subpage	Start on the relevant offer page. “You have read this page and want to understand what the company provides overall. What would you do?”	Where they look; expected destination before clicking; actual route; what they can explain afterward.
Direct evaluation	Start from a page or navigation point realistic for this evaluator. “You need to determine [supplied requirement] before recommending further evaluation. Find what you would use to make that judgment.”	Expected destination; route; answer found or missing; what they conclude and what remains unresolved.

Observation or readiness gap	What it may mean	Decision to investigate
Participant cannot predict what a label leads to	Possible destination-cue problem.	Check label and context against the actual content.
Participant finds the right place but cannot explain the answer	Possible explanation or assumed-knowledge problem.	Check prerequisite context, wording and evidence.
Required answer is unavailable	Content/owner gap.	Obtain the facts; navigation changes alone cannot resolve it.
Participant understands a verified incompatibility	Correct fit judgment, not necessarily confusion.	Preserve the requirement and honest no-fit conclusion.

Record exact observations separately from interpretations and proposed revisions. These cards are proposed tests, not results. No universal click count, confidence percentage or conversion lift is established. A sitemap review is not evidence that real visitors can use it.

BuyerTwin can help examine proposed pages against target-buyer models. Record the actual input and findings if you run it; a modeled response is not an observed human journey. Generic AI role-play is neither human research nor an actual BuyerTwin analysis.

Sources and evidence limits

This method is Insivia's practitioner synthesis of Andy Halko's guide-wide buyer-centric viewpoint.

• Information Scent — NNGroup informs recognizable destination labels and the effect of context and prior knowledge on expectations.
• Progressive Disclosure — NNGroup informs accessible layers of detail with clear routes. It does not justify hiding a decision-critical answer.

These sources do not validate this specific planning worksheet or predict conversion. Example facts are fictional. Version 0.5; retain Insivia attribution, source identity, and evidence limits when adapting this standalone file.

Optional next tasks

Each linked playbook answers a different next question. This file already contains its own essential method and working resources; no other download is required.

• Optimize your homepage when the company overview and onward routes need development.
• Build a buyer-centric product or solution page when a specific offer needs a deeper explanation.
• Create relevant industry, role and use-case pages when a genuinely different audience question may justify a tailored page.
• Plan a buyer-centric rebuild and launch when the agreed page-responsibility map needs a delivery, URL and release plan.
• Test and improve buyer alignment when you are ready to check whether buyers can find and interpret the proposed answers.