Services

Four practices

We do four things. All of them well.

↘ What we offer

Strategy, brand, product, and growth — delivered by senior practitioners who stay until the work ships.

Booking projects — Q3 2026

01

↗

400+ pages

Documentation restructured and remediated across two merged webMethods libraries

Includes

02

↗

45+ terms

Entries in the terminology and inclusive-language standard I wrote and own

Includes

03

↗

28-person team

Writers and designers working to that standard, enforced by templates rather than reminders

Includes

Product design

UX, UI, and interaction design.

Web & iOS builds

Marketing sites, SPAs, and native apps.

Design systems

Validate before you build at scale.

Prototyping & testing

Components, tokens, and documentation.

04

↗

10+ teams

Product writing teams across the webMethods suite that adopted the task-based IA model I built

Includes

Go-to-market

Launch strategy, channels, and sequencing.

Pricing strategy

Packaging, tiers, and monetisation models.

Lifecycle & retention

Onboarding, activation, and churn reduction.

Channel & distribution

Where and how to reach the right audience.

Language decisions, up close

Three patterns from the terminology and accessibility standard I wrote for webMethods. The case studies tell you how I think. These tell you how I write, and what I do when a change is technically correct but politically annoying.

Terminology · replication settings

BEFORE

Configure the master node to push changes to all slave nodes.

AFTER

Configure the primary node to push changes to all replica nodes.

WHY IT MATTERED

Industry-standard replacements, chosen because they are also more accurate: a replica is defined by what it does, a slave by a relationship it doesn't have. This became one of 45+ entries in the terminology table, so writers stopped deciding case by case.

Pronouns · procedure steps

BEFORE

The administrator must ensure that he has configured his gateway before he deploys an API.

AFTER

Configure your gateway before you deploy an API.

WHY IT MATTERED

The inclusive fix and the clarity fix were the same edit. Second person removed the gendered pronoun, cut fourteen words to nine, and turned a description of a person into an instruction to the reader.

Alt text · architecture diagram

BEFORE

alt=“Diagram”

AFTER

alt=“API requests pass from the gateway to three backend services; the control plane monitors all three and reports failures back to the gateway.”

WHY IT MATTERED

“Diagram” passes an automated check and tells a screen-reader user nothing. The rule I wrote into the standard: describe what the diagram argues, not what it contains, and never make alt text the only place information lives.

Language decisions, up close

Three patterns from the terminology and accessibility standard I wrote for webMethods. The case studies tell you how I think. These tell you how I write, and what I do when a change is technically correct but politically annoying.

Terminology · replication settings

BEFORE

Configure the master node to push changes to all slave nodes.

AFTER

Configure the primary node to push changes to all replica nodes.

WHY IT MATTERED

Industry-standard replacements, chosen because they are also more accurate: a replica is defined by what it does, a slave by a relationship it doesn't have. This became one of 45+ entries in the terminology table, so writers stopped deciding case by case.

Pronouns · procedure steps

BEFORE

The administrator must ensure that he has configured his gateway before he deploys an API.

AFTER

Configure your gateway before you deploy an API.

WHY IT MATTERED

The inclusive fix and the clarity fix were the same edit. Second person removed the gendered pronoun, cut fourteen words to nine, and turned a description of a person into an instruction to the reader.

Alt text · architecture diagram

BEFORE

alt=“Diagram”

AFTER

alt=“API requests pass from the gateway to three backend services; the control plane monitors all three and reports failures back to the gateway.”

WHY IT MATTERED

“Diagram” passes an automated check and tells a screen-reader user nothing. The rule I wrote into the standard: describe what the diagram argues, not what it contains, and never make alt text the only place information lives.

Language decisions, up close

Three patterns from the terminology and accessibility standard I wrote for webMethods. The case studies tell you how I think. These tell you how I write, and what I do when a change is technically correct but politically annoying.

Terminology · replication settings

BEFORE

Configure the master node to push changes to all slave nodes.

AFTER

Configure the primary node to push changes to all replica nodes.

WHY IT MATTERED

Industry-standard replacements, chosen because they are also more accurate: a replica is defined by what it does, a slave by a relationship it doesn't have. This became one of 45+ entries in the terminology table, so writers stopped deciding case by case.

Pronouns · procedure steps

BEFORE

The administrator must ensure that he has configured his gateway before he deploys an API.

AFTER

Configure your gateway before you deploy an API.

WHY IT MATTERED

The inclusive fix and the clarity fix were the same edit. Second person removed the gendered pronoun, cut fourteen words to nine, and turned a description of a person into an instruction to the reader.

03 — Output

BEFORE

alt=“Diagram”

AFTER

alt=“API requests pass from the gateway to three backend services; the control plane monitors all three and reports failures back to the gateway.”

WHY IT MATTERED

“Diagram” passes an automated check and tells a screen-reader user nothing. The rule I wrote into the standard: describe what the diagram argues, not what it contains, and never make alt text the only place information lives.

How we engage

Three ways to work together.

Most engagements are scoped and fixed. We don't do day rates or open-ended retainers — they incentivise the wrong things.

Sprint

A focused problem, solved fast.

Two to four weeks. A single defined output — a positioning doc, an identity, a pricing model, a launch site. No bloat, no extensions.

2 – 4 weeks

From £12,000

Engagement

A bigger challenge, properly resourced.

Six to twelve weeks. Multi-practice work — strategy and brand, brand and product, growth and positioning. Where the real complexity lives.

6 – 12 weeks

From £45,000

Advisory

Ongoing access to senior thinking.

Monthly structured sessions with a partner. For companies that need consistent strategic input without a full engagement. Capped at three clients.

Ongoing / monthly

From £4,500 / month

Advisory

Ongoing access to senior thinking.

Monthly structured sessions with a partner. For companies that need consistent strategic input without a full engagement. Capped at three clients.

Ongoing / monthly

From £4,500 / month

Get in touch

OPEN TO NEW OPPORTUNITIES

Let's talk about what's next.

Email

mahimashastryux@gmail.com

Get in touch

OPEN TO NEW OPPORTUNITIES

Find my work interesting? Let's talk

Email

mahimashastryux@gmail.com

Get in touch

OPEN TO NEW OPPORTUNITIES

Let's talk about what's next.

Email

mahimashastryux@gmail.com

MAHIMA SHASTRY

BANGALORE, INDIA

MAHIMA

Mahima. All rights reserved.

No templates were harmed in the process of making this portfolio

MAHIMA SHASTRY

BANGALORE, INDIA

MAHIMA

Mahima. All rights reserved.

No templates were harmed in the process of making this portfolio

MAHIMA SHASTRY

BANGALORE, INDIA

MAHIMA

Mahima. All rights reserved.

No templates were harmed in the process of making this portfolio

Create a free website with Framer, the website builder loved by startups, designers and agencies.