After a difficult year, reset positioning around the operation that exists today. Audit the old promises. Find the project types and handoffs that caused the strain. Fix the process. Then publish only the claims your current documents and capacity support. Buyers do not need a glossy reinvention. They need clear fit, visible controls and accountable answers.
What changes before the website changes?
The operation. Review the projects that created pressure and separate outside conditions from controllable failures. A delayed decision exposes a weak selection reminder. A disputed scope item exposes inconsistent specifications. Repeated punch carryover exposes unclear ownership or verification.
Do not start with a new slogan. Fix the handoff, document the new method and decide who owns it. The positioning library reconnects those operating choices to the public message once the work is real.
How do you audit claims left over from the old operation?
Inventory every claim on the website, the sales deck, the Google Business Profile, the brochure, the signs and the Parade handout. Match each one to a current source and a responsible role. A statement about updates, selection support, schedule visibility, warranty response or project type may have been true under a different team or a lighter workload.
| Claim area | Evidence to check | Possible action |
|---|---|---|
| Project fit | Current pipeline, staffing and lot context | Narrow the accepted work |
| Plan coordination | Revision ownership and distribution record | Clarify the release gate |
| Selections | Status labels, deadlines and approval trail | Correct the public sequence |
| Field updates | Actual owner, format and trigger | Remove an unsupported cadence |
| Punch and warranty | Intake, classification and closeout | Explain the reviewed path |
The build-process guide gives a structured way to rebuild the operating source behind these claims.
How does a builder reset its position?
- Define current capacity. The project mix, lot context and buyer involvement the team can serve well now.
- Find broken handoffs. Plan revisions, selections, changes, draws, updates, punch and warranty transitions.
- Correct the operating source. Owners, inputs, outputs and exception paths.
- Retire unsupported claims. Anything that describes the old team, an occasional practice or an aspiration.
- Choose new proof. Current documents, controls and completed corrections, with private project material left out.
- Brief every channel. Website, inquiry response, sales conversation and event script, all aligned.
- Set review triggers. Recheck the position when pipeline, staffing or process changes again.
The Positioning stage turns this reset into an owned brief for project fit, proof and exclusions.
How much do you say about the difficult year?
Address specific public issues where a responsible response is needed. Do not build the whole message around defense. Confirm the facts, respect privacy and get appropriate advice on disputed matters. The website is not the place to argue a private project record.
For general positioning, describe the process now in place. If plan revisions used to move without a controlled release, explain the current plan-control step. If warranty requests had no clear entrance, publish the current intake and review path. Never claim that a corrected process guarantees every outcome.
Should old project galleries come down?
Review each entry. Keep work that is accurately represented, approved for publication and relevant to the current position. Remove or relabel anything that implies a service, a team or a project type the company no longer offers. Keep internal records of what changed.
Which evidence supports each correction?
Proof close to the fix. A defined plan-release log supports a coordination claim. A selection tracker with clear states supports a decision-management claim. A punch closeout method supports a completion claim. A warranty intake form and classification path support an aftercare explanation.
Do not swap old hype for new hype. The article on builder proof points connects each statement to a reviewable source. The article on communicating build quality explains field controls without claiming perfection.
How can an AI agent fleet support the reset?
The AgAI Labs fleet of Claude and Codex AI agents inventories pages, extracts claims, compares terms across documents and drafts a list of conflicts. They organize project notes by stage and flag missing owners or sources. People establish the facts, set direction and review every output.
Agents do not decide fault, answer disputed reviews or turn incomplete records into a public explanation. Use them to expose inconsistency and speed up controlled drafting. Sensitive buyer, trade and financial material stays out of public content.
How do you keep the reset from drifting?
Give the positioning brief an owner and a revision log. Tie each public claim to its source. In pipeline reviews, ask whether the accepted work still matches the stated fit. At project closeout, note repeated questions that suggest the website is attracting the wrong expectation.
Parade weekends are a useful stress test. If house hosts improvise three different explanations of customization, communication or warranty, the message is not operational yet. Update the brief and the script together. The article on saying who you do not build for keeps poor-fit work from undoing the reset.
Which questions come up during a positioning reset?
Should we announce a rebrand after a difficult year?
Only after you have verified the operating changes behind it. The revised message rests on corrected handoffs and current evidence, not a new logo.
Do we need to remove every old claim?
No. Audit each one against current practice. Keep what is supported, revise what is inaccurate and retire what has no current evidence.
Can we respond to criticism with project details?
Protect private project information and get appropriate review for disputed matters. Buyer records stay out of public positioning.
When is the reset complete?
When operations, documents, sales language and public pages all agree. Assign owners and future review triggers at that point.