Shruti KaushikWise Mango writes LinkedIn content for architects and practice principals who want clients, collaborators and recruits to understand how they think, without breaching title protection, client confidentiality or professional conduct rules. Shruti Kaushik interviews you, drafts to a written voice guide that records the code you work under, edits every piece and sends it to you for an accuracy check and sign-off before you publish. Two 60-minute discovery calls start the engagement; pricing is shared on a call.
What LinkedIn has to do for architects
Architecture is sold on trust and judgement before it is sold on drawings. The people an architect needs to reach on LinkedIn are developers and private clients choosing who to appoint, contractors and engineers who will work on the project, planners and policy people, and graduates deciding where to train. Fellow architects read too, and their referrals matter.
The profile has to show how you resolve a problem: a difficult site, a planning constraint, a budget that changed. Pictures help, but the writing is what explains the decision, and it is the part a ghostwriter can carry for a busy principal.
What you can and cannot say, and what changes in the process
The rules differ by country, and in the UK the starting point is the Architects Registration Board. ARB says it protects the legally restricted title "architect" and that it must issue the Architects Code under the Architects Act 1997, setting out the standards of professional conduct and practice expected of registered architects. ARB describes the Code as a guide to good practice, says every architect on the UK Register must follow it wherever they live or work, and says breaches can be considered in disciplinary proceedings before its Professional Conduct Committee.
Outside the UK, bodies such as the American Institute of Architects and the Council of Architecture in India publish their own codes and registration rules. Wise Mango does not interpret any of them. We record the code you work under in the voice guide and draft inside it.
- The word architect is used only for people entitled to the title; other team members are described by their actual role.
- No claims of competence, awards or affiliations that you cannot document.
- No project images, drawings or client names without written client consent and confirmed image rights.
- Credit for collaborators, consultants and the wider team is stated accurately.
- Nothing that reads as a criticism of a named practice or client.
Sample topic angles
- The constraint that made the design better. A site, budget or planning limit and how it changed the scheme.
- What clients should ask before they appoint an architect. Practical questions that help a client choose well.
- A detail that took longer than it looks. One junction, material or sequence and why it matters on site.
- How you train juniors to see a site. A habit you teach and why it survives the software.
These are starting points; the real list comes from the interviews and from what you can show with consent.
Common mistakes
- Posting a client's project before the client has agreed.
- Using images from a photographer without checking the licence.
- Letting a team member describe themselves as an architect when they are not registered.
- Claiming sole credit for a project that involved a wider team.
- Writing in vague design language that tells a client nothing about how you work.
How the engagement runs
- Two discovery calls, 60 minutes each. Business context, who you need to reach, the point of view you should be known for, and how you sound when you talk about your work. These produce a written voice guide.
- A written proposal. Deliverables, review rounds, responsibilities, fees and exclusions, in writing before you commit. Pricing is shared on a call, not on this page.
- Interviews, then drafts. Each cycle opens with a short conversation and closes with drafts matched to the voice guide. Shruti Kaushik writes and edits; AI supports the drafting where it saves time; a human editor reads every piece.
- Your approval. You check every fact and approve every piece before it is published. You publish from your own account. Wise Mango never asks for your LinkedIn login.
Wise Mango works remotely with clients worldwide. No reach, lead or revenue outcome is promised; progress is reviewed against measures agreed with you.
A free resource whichever route you take: the Klype post checker, built by the same founder, flags unsupported claims, invented stories and machine-writing patterns in any LinkedIn draft, with no sign-up.
Book a 30-minute strategy call ↗
Prefer email? Write to shruti@wisemango.io with a line about your work and who you need to reach.
Common questions
Do you follow the ARB Code or the AIA code?
We follow whichever applies to you. Tell us your regulator (for example ARB in the UK, the AIA in the US, or the Council of Architecture in India) and the voice guide records it. We do not interpret the code; your sign-off is final.
Can you use project photographs and client names?
Only with the client's written consent and the photographer's rights confirmed. Where consent is not in hand, we write about the design problem instead of the project.
Who is the audience for an architect on LinkedIn?
Developers and private clients, contractors, engineers and other consultants, planners, recruits and fellow architects. The content is written for them.
Who writes the content?
Shruti Kaushik writes and edits the work. AI supports drafting; a human editor reads every piece; you approve before it is published from your own account.