“We provide architectural design from concept to completion” sounds clear until a prospective client starts asking practical questions. Does that include a planning submission? Who appoints the structural engineer? What does the practice need before it can estimate a fee? A service page should answer those questions before asking for an enquiry.
Unlike a project gallery or an educational article, a service page defines an engagement: who it suits, what the practice does, what the client receives, and where other parties take responsibility. It should help a homeowner, developer, investor, or public-sector buyer judge whether the service fits their project—and what they need to start a conversation.
Start with the decision the buyer is making
Define both the service and the buyer’s situation before drafting. “Architectural services” might mean feasibility advice for an undeveloped site, design for a new school, or support during construction of an approved building. Each buyer faces different constraints. A developer assessing land may be concerned with capacity and planning risk; a healthcare operator may need to understand how clinical workflows and operational requirements shape the brief.
Write the likely decision in one sentence: “The buyer needs to decide whether to commission a feasibility study before purchasing this site.” Then list what they must know to make it. That is a better starting point than describing the practice’s capabilities and adding buyer questions later.
Actual enquiries, tender clarifications, initial meetings, and project handovers provide useful evidence. Group recurring questions by service rather than copying them all into a long FAQ. Put survey requirements near the explanation of how work begins, and planning approval questions near the scope and limitations. The guide to turning client questions into useful architecture articles sets out a fuller method for identifying those information needs.
Separate qualification questions from process questions
Buyers first need to establish fit: Does the practice work on this building type, at this scale, and at this stage? Then they need to understand delivery: What happens first, what decisions will they make, and what will they receive? A page can explain the design process well and still fail if it never says whom the service is for.
An opening could say: “This service is for owners and development teams assessing whether an existing commercial building can be adapted to a new use.” Follow it by stating whether the work stops at initial options or continues through approvals and detailed design. If experience, staffing, or procurement requirements limit the work the practice can take on, say so rather than claiming to serve every building type.
Put scope ahead of reassuring adjectives
“Full service” and “end-to-end” mean little without boundaries. Describe the work in an order a client can follow: reviewing the brief and available site records, developing options, coordinating agreed consultants, preparing drawings for a specified submission, and responding to comments within an agreed period. Scope varies by commission and jurisdiction, so present this as a usual arrangement, not a universal contract.
Pair activities with deliverables. “We develop a concept” tells a buyer less than “The concept stage typically produces option drawings, an outline area schedule, and a record of decisions for the client to review.” If visualizations, cost plans, technical specifications, or tender documents are not standard, explain whether they require a separate appointment. Buyers can then compare proposals without assuming that similarly named services contain the same work.
Explain what is excluded and who does adjacent work
Architectural work often depends on measured surveys, ground investigations, structural and building-services engineering, specialist planning advice, cost consultancy, and statutory fees. Identify the dependencies relevant to the service. Otherwise, a buyer may mistake the design fee for the complete project budget.
Be precise about responsibility. “We coordinate engineering information where appointed to do so” does not mean engineering design is included. For permit or planning applications, distinguish preparing submission material from the authority’s decision. Approval criteria, review periods, and required documents depend on the location and proposal; neither approval nor a fixed decision date can responsibly be promised.
Make the sequence and decision points visible
After reading the page, a buyer should be able to picture what follows an enquiry. A few meaningful stages are more useful than an exhaustive internal workflow:
- Initial review: The practice checks the location, building type, project stage, brief, and information already available.
- Scope agreement: The parties define deliverables, consultant responsibilities, assumptions, review points, fees, and work outside the appointment.
- Investigation and options: The team tests the agreed brief against site constraints, regulatory requirements, and available budget information.
- Client decisions: The client reviews defined options and authorizes a preferred direction before more detailed work proceeds.
- Next-stage handover: Drawings, reports, or submission documents are issued in the format agreed for the commission.
Allow for branches. A feasibility study may find that the preferred use is unlikely to fit the site, or that a survey is needed before an area figure can be relied on. Revising the brief may then make more sense than moving straight to a planning submission. Those decision points are more credible than a perfectly linear diagram that ignores uncertainty.
For construction-phase services, distinguish periodic site visits and responses to design queries from continuous supervision. Say whether contract administration, inspection, certification, and post-occupancy review are offered, and under what type of appointment. “Oversee the build” may suggest responsibilities the agreed scope does not include.
Answer cost and timing questions without false precision
Even when an exact fee cannot be published, buyers need to understand how a quote is formed. Relevant factors include building size and complexity, the completeness of existing information, consultant coordination, the number of options, submission requirements, and the level of construction support. Explain whether the practice uses fixed fees for defined stages, time-based fees for uncertain work, or another structure—and when each applies if the approach varies.
Keep the architectural fee distinct from construction cost, consultant fees, application charges, survey costs, and contingencies. A design fee does not establish the final cost of a building. Early budgets are tested and refined as information develops; changes in scope, specification, site findings, or market pricing can alter them materially.
Timing calls for the same care. For example: “The concept schedule is agreed after we review the brief, survey information, and required decision dates. Authority review and specialist reports are scheduled separately.” If you publish a typical range, name the stage and its assumptions. Without a defined start, finish, and allowance for client review, a range is easy to misread.
Use proof that answers a specific doubt
Include project examples, diagrams, and credentials when they help a buyer assess capability. Match each example to the claim it supports. For a building adaptation service, a brief account could identify the original use, the client’s objective, the principal constraint, the team’s role, and what was delivered. A photograph alone cannot show what the architect did or how closely the project resembles the buyer’s.
Handle outcomes carefully. A completed project can show experience with a building type or coordination challenge; it cannot guarantee the same consent, programme, cost, or performance elsewhere. Label figures by what they measure and when they were recorded: an estimated construction cost at concept stage is not a final construction cost. Obtain permission before publishing confidential client information or identifiable drawings.
A clear account of the method can also provide evidence. On a medical-facility design page, explaining how the team establishes room requirements, patient and staff circulation, equipment needs, and operational constraints may be more useful than a broad claim of specialist expertise. If regulations or technical standards are mentioned, do not suggest that one checklist applies to every jurisdiction or facility.
Write for several buyers without producing one vague page
Public clients, private owners, and developers may buy similar design services but look for different evidence. A public-sector buyer may need to know about procurement compatibility, stakeholder engagement, and reporting. An owner-occupier may focus on disruption, approvals, and their own decisions. A developer may prioritize site capacity, programme dependencies, and cost information.
When the underlying scope is substantially the same, one clear page can include short sections for those different circumstances. If deliverables, procurement routes, and specialist requirements differ materially, separate pages may be more useful. Rather than repeating the same introduction across pages, explain what changes for a school extension, a commercial refurbishment, or a housing feasibility commission.
Keep the language aligned with the buyer’s stage
An early-stage buyer may not know whether they need a concept design, feasibility study, or planning support. Define each by its purpose and output. A feasibility study tests constraints and potential options before a preferred design is chosen; it does not replace the technical documents needed to build. Buyers further along may need detail on drawing packages, consultant coordination, and construction queries. Make those differences explicit instead of relying on professional terminology.
Build a page readers can scan and act on
Give each major question a clear place: who the service suits, what problem it addresses, scope and deliverables, working stages, responsibilities and exclusions, cost and timing factors, relevant evidence, and the information needed to enquire. Headings should say what a section contains, rather than repeating “Our approach.” Keep paragraphs readable without stripping out the conditions behind an answer.
When stages sound similar, a small comparison table can clarify the boundaries:
| Stage | Typical question answered | Possible output |
|---|---|---|
| Feasibility | What options appear viable with the information available? | Options and a record of key constraints |
| Concept design | Which proposed arrangement should be developed? | Concept drawings and agreed design direction |
| Technical design | How will the agreed design be documented and coordinated? | Defined drawing and specification package |
Mark such outputs as illustrative; the appointment determines what is delivered. A table should clear up confusion, not imply a commitment to documents outside the standard scope.
The final action should fit the service described. If the team needs a site address, intended use, approximate floor area, project stage, target dates, and available surveys to assess an enquiry, ask for those items. Say what follows, such as an initial scope review before a proposal. Do not demand a complete technical brief from someone seeking help to define one.
Check the draft against real enquiries before publishing
Ask someone who did not draft the page to read it alongside a recent enquiry. Can they identify the likely deliverables, main exclusions, client decisions, and information needed for a fee proposal? Check their answers against current appointment documents. If the page offers a “planning approval service” but the standard proposal covers only drawings for submission, correct the page or clarify the appointment before publishing.
Give someone responsibility for reviewing the page when services, team capacity, regulations, or procurement requirements change. Recurring client questions will expose gaps. If several people ask whether a structural engineer is included, put the answer beside the scope rather than burying it in a general FAQ. Keep a simple record of clarification requests to guide revisions.
For the last line-level check, take a claim such as “we help secure approvals” and name the work actually performed: “We prepare the agreed architectural drawings for the application and respond to design-related queries within the appointed scope.” The buyer can compare that sentence directly with the proposal.