A builder about page should answer four questions: what you build, who reviews the lot and plans, who tracks selections and draws, and who picks up the phone after the warranty walk. Tie each answer to a page a buyer can check. Skip the origin story unless it explains how you work today.
What is a buyer trying to learn on the about page?
A buyer at the $1M mark is checking whether your team can carry their job. Calling the team passionate or detail oriented tells them nothing. They want to know who reviews the lot, who explains a plan change, who tracks selections, who calls when the framing inspection slips and who owns the warranty handoff.
Answer at the company level first. State the project types, lots and plan paths that fit. Say which project types, lot conditions and service areas fall outside your work when a clear boundary saves both sides a wasted meeting. Then introduce roles as steps in the job, not as a row of biographies.
What should the opening section establish?
- The kind of custom or semi-custom work the company performs.
- The lot, plan or community context the team evaluates.
- The decision sequence and documentation the process uses.
- The operating principles a visitor can inspect elsewhere on the site.
Link each principle to evidence. If the page says the team communicates clearly, point to the build process page and the weekly update. If it says decisions are documented, show how a selection or a change order lands in the project record.
How should team roles be presented?
Organize people by what they own in the job. A role description tells the buyer where a question goes; a résumé paragraph does not. Match the public description to the real handoffs between sales, preconstruction, design, field, closeout and warranty.
| Team function | Buyer needs to know | Evidence to link |
|---|---|---|
| Project fit | Who reviews lot, location and plan readiness | Intake and fit process |
| Preconstruction | Who coordinates scope, allowances and approvals | Process and specifications pages |
| Design and selections | Who records choices and decision deadlines | Selection method |
| Field coordination | Who communicates progress and site questions | Build update method |
| Completion | Who coordinates quality review and handoff | Punch and orientation process |
| Aftercare | Who owns warranty intake and service records | Warranty page |
If one person owns several functions, say so. Do not inflate a three-person company into departments. Buyers like a direct line; they need to know where that line changes once the job moves to the field.
Which experience claims belong on the page?
Use claims you can verify and keep current. Experience matters when it explains judgment: reading a sloped lot, holding a plan revision together, setting selection deadlines, explaining a draw or separating punch work from warranty calls. Connect years and project history to those decisions.
Cut superlatives, broad quality claims and totals nobody maintains. Do not pad the page with old jobs, awards or press that say nothing about the company a buyer would hire today.
- Name the capability. State the work the team performs.
- Show the source. Link a process, plan, specification or project record that demonstrates it.
- Define the boundary. Explain the lot, design or project context where it applies.
- Assign review. Give one role responsibility for keeping the claim current.
The project gallery page guide shows how completed work can support an about-page claim without turning it into a vague portfolio statement.
How much company story should you tell?
Tell the part that explains how you operate now. An origin story earns its place when it shows why you chose a project type, a service area or a method. It turns into filler when it never reaches what the team does differently during plan review, construction or aftercare.
Keep it to four beats: why the company began, what the field taught you, how the current process reflects that lesson and where a buyer can inspect the result. Family history, community work and trade background stay only when the people involved approve publication and the detail explains current practice.
How should company values appear?
Translate every value into something a buyer can observe. “Transparent” can mean a published allowance schedule, recorded change orders and a weekly update on a set day. “Craftsmanship” needs a quality-control checklist, not a close-up of a miter. “Service” should point to who takes the warranty call and how fast the first reply goes out.
How should the about page connect to the rest of the site?
The about page does not carry the whole proof burden. Link project types to plans and projects. Link operating claims to the builder process page. Link scope language to the specs page. Link service-area statements to community and lot pages you keep current.
Return links matter too. A project page can name the role that made a key decision. A warranty page can point the aftercare role back to the team. Check that each linked page names the same responsible role as the about page.
The rest of the builder websites articles cover each connected page; the custom builder website guide lays out the full set.
How do you keep the page honest as the team changes?
Give the page an owner. Review it whenever responsibilities, service areas or handoffs change. Remove departed staff and update public roles the same week. If a role is open or shared for now, describe the function without promising a structure you have not staffed.
Our AI agents can sort approved notes, draft role summaries, compare terms across pages and check links. People decide what is true, protect private information and approve every claim. The Positioning stage produces the fit statements this page rests on.
Common questions about builder about pages
Does every team member need a biography?
Your builder about page needs role descriptions for responsibilities buyers encounter. Use approved information and explain handoffs; internal or temporary roles do not need separate biographies.
Should the about page list awards?
Your builder about page can include current, verifiable recognition when it helps buyers evaluate the company. Identify what the recognition covers and keep its source available.
Can we say we build high-quality homes?
Builder quality claims need observable support. Show the quality-control method, specification discipline, documented project decisions and closeout process, then assign someone to verify those descriptions.
What if one person handles sales and construction?
If one person handles builder sales and construction, describe both responsibilities, availability and the way decisions are recorded. Explain where buyers send questions at each handoff.