Professional services
Architecture and engineering
Designing buildings and infrastructure before they are built.
Four practices that get paid to say a thing will stand, perform, or sit where the deed says it does. Their buyers range from a project director running a tender to a land buyer with one urgent question. What they share is a technical question asked long before any consultant is called, and answered today by product vendors and code-summary sites.
Where the answer is being lost
Your engineering answers are written by people who do not sign.
A developer's project head types "How do you size HVAC for a data centre in a hot and humid climate" and gets an answer stitched from equipment brochures and a design note written for a dry climate. A PMC lead scoping a retrofit reads a generic checklist. Neither answer came from anyone who has stamped a drawing. The practices that could have written both are absent while the technical decision is live, and turn up months later as one more name on a tender list, arguing about fee.
How we win this
The programme for architecture and engineering
Answer the code question
Every one of these practices holds interpretation that no vendor and no code summary can reproduce: what a clause means on a building that already exists, what a local authority will actually accept, where two standards disagree. Published as answer pages and cited to the standard it came from, that interpretation is the one thing an engine cannot source elsewhere.
Depth, or say nothing
The reader here checks the working. A page that restates a definition tells a data centre project head that your firm assembles drawings rather than engineers them, and that costs more than publishing nothing at all. So we run fewer pieces, written or reviewed by the engineer who does the work, showing assumptions and the point where judgement enters.
The reader is usually not the client
The person doing the reading here often cannot appoint anybody. An architect recommends the structural engineer and the project director signs. A main contractor names the MEP consultant on a building somebody else owns. An advocate tells a landowner whose survey plan a court will accept. Each of them is answering a question somebody else put to them, and answering it out of whatever they last read that made sense. Written to persuade a client, a page reads as a brochure to that reader. Written to settle the question they have been handed, it gets passed on with your name still on it.
Where the tender decides
Planning work is empanelled, and much structural work is relationship-led. A page does not change who gets invited to price a scheme. It changes three narrower things, and they are worth naming exactly: what a project officer finds when your name comes up on a list of four, what a recommending architect reads in the week before the recommendation, and whether a private developer who answers to nobody can find you and ring direct. In planning that is the whole of the gain. In structural it is most of the first year.
The mix that carries it
Content
Answer and comparison pages
Cost, process, eligibility and comparison pages built for direct extraction, not for a reader who scrolls.
Content
GEO blogs and authority content
The definitive written answer to the questions your buyers put to an engine, structured so it can be lifted and attributed.
Foundation
Entity and schema engineering
Structured data and entity definition so engines know exactly what you are, where you operate, and what you are credible in.
Authority
Directories and profile consistency
Every listing, registry and profile saying the same thing, so the entity resolves to one business instead of three.
Foundation
Website build and optimisation
Sites architected for SEO and GEO from the ground up: fast, structured, hardened, and legible to a model.
Authority
Original data and benchmarks
Proprietary numbers, surveys and benchmarks — the most-cited asset class there is, because nobody else has them.
Authority
Digital public outreach
Earned mentions, trade coverage and third-party citations — the corroboration a model checks before it names you.
Distribution
Practitioner and executive content where B2B buyers and the models watching them both look.
The constraint we work inside
Nothing we publish can read as advice on a specific structure or site, and drawings, load calculations and client project data stay where they are. What goes out is method and code interpretation, generalised, attributed to a named engineer, cited to the standard, and dated so it can be rebuilt when the code moves.
Specialisations
4 total
The pitch is different for each one, because the buyer, the trigger and the rules on what may be published are different for each one. Open the one that is yours.
A PMC lead scoping a vertical extension asks what checks the job needs, months before anyone is invited to price it, and reads an answer no engineer wrote.
The question deciding this today
“What structural checks are required for a vertical extension on an existing building”
- Who they sell to
- Developers, contractors, infrastructure asset owners
- Who signs
- Project director, principal architect, PMC lead
- What starts it
- Project award, retrofit, code revision, investigation after a failure
- Cost of staying invisible
- Safety liability, expensive redesign, approvals held up
Type "What structural checks are required for a vertical extension on an existing building" and the reply arrives from a code-summary site, a builder's blog and a foreign standard. None of it accounts for the existing foundation, the seismic zone, or what the local authority will accept. The principal architect reading it is the person who recommends a consultant to the project director. If your practice is not in that answer, the recommendation forms without you, and the invitation to tender follows the recommendation.
What we would run
- 01Answer and comparison pages
A set covering the questions that precede an appointment: what a vertical extension assessment involves, when non-destructive testing suffices and when core sampling is needed, what a retrofit report must contain for approval.
The architect and the PMC lead research scope before any consultant is named. This is the stage at which a practice becomes an option rather than a bid.
- 02GEO blogs and authority content
Engineer-authored pieces on the judgement calls: reading a code revision against a building already standing, deciding what an investigation after a failure has to establish, choosing between strengthening and rebuilding.
Project directors do not need the clause text. They need to see how a practice reasons before handing over a structure that is already occupied.
- 03Entity and schema engineering
Structured records tying each named engineer to disciplines, structure types and the codes they work to, kept identical on the site, in the practice's registry entries and on the engineer's own profile.
A project director wants an answer that ends in a person he can look up on a register. An engine returns a person only where a person exists in the data, attached to a registration. Publish at practice level alone and the most that comes back is a firm name, which is the part nobody can check.
- 04LinkedIn
The principal's own posts on live technical questions: what a code amendment changes for projects already in design, what a failure investigation had to establish, described in general terms.
Architects and PMC leads get asked who they would use, and they answer out of memory. What sits in memory is whoever was last seen working through something difficult in public.
What we would not recommend
- Reviews and testimonials. Structural sign-off carries liability. A client rating adds nothing to a project director's technical check, and cannot be verified by anyone reading it.
- Reddit. Project directors and PMC leads do not source consultants there, and threads cannot carry the code detail this work actually turns on.
- Instagram. The only material that would work here is a client's structure part way through strengthening. Site photographs and drawings are precisely what stays private, so what is left to post is stock imagery of buildings you never touched.
What a lead looks like
The call comes at feasibility, not at tender. A principal architect on a residential redevelopment has your vertical-extension page open and has read the note on the latest code revision. She asks whether the existing raft can take two more floors, and what an assessment would cost. The consultant list does not exist yet.
What we measure
- Inclusion on retrofit and extension prompts
- Named engineers cited by discipline
- Enquiries arriving at feasibility stage
- Answer coverage against the live code set
What changes
A principal architect rings at feasibility to ask whether a raft will take two more floors, instead of appearing at tender to argue about fee. A facility owner wants a design assumption tested before the chiller is ordered. A land buyer reads out a survey number in the first thirty seconds of the call. Planning is the honest exception: the gain there is that your practice survives the officer's name check, and that a developer with budget discretion can reach you without a tender.
Start here
See who gets named in architecture and engineering today
We put your buyers' real questions to the live models and come back with the businesses they name, the sources behind those answers, and the gap between that list and yours.