| name | communication-voice |
| description | Write outbound email and external messages in Vamsee Achanta's voice — a subtle offer to help, never bold or rash claims. Load before drafting ANY email, LinkedIn/Collide reply, proposal note, or outreach sent under his name. |
| type | guideline |
| version | 1.0.0 |
| category | guidelines |
| last_updated | "2026-07-30T00:00:00.000Z" |
| source | internal |
| tags | ["communication","email","outreach","voice","business-development","writing"] |
| freedom | low |
Communication voice — writing as Vamsee Achanta
Load this before drafting any message that goes out under Vamsee's name: cold outreach,
replies to Collide/LinkedIn posts, client notes, academic requests, proposal follow-ups.
Canonical business-side guide (fuller rationale + genre notes):
aceengineer-strategy/docs/standards/communication-voice.md.
The thesis
A subtle offer to help — not bold, rash statements.
Everything below is a mechanism for achieving that. If a draft violates the thesis, it is wrong
even if it follows every rule here.
The five mechanisms
1. Offers are availability, never assertion.
"I can help in various areas." / "How I may be able to help, one operation at a time.
Some examples are given below:" — pre-labelling the list as examples strips it of
proposal-status before it is read. Never "I will deliver X".
2. Never assert the recipient's problem. Convert diagnosis into something to check.
- ✗ "Your truck plan is the bottleneck."
- ✓ "…to check whether one truck carries you to 150-200 BOPD or becomes the bottleneck."
Offer both branches; let the data decide. Generalities ("the first barrels are usually
setpoints and spacing") are fine; verdicts on their operation are not.
3. Hedge the promise. Never hedge the fact.
| Hedged — outcomes, and anything about them | Unhedged — facts, terms, capability, own limits |
|---|
| "can potentially make", "roughly +30 BOPD", "usually", "may be able to", "I think" | "I have worked at Occidental for over 5 years." "I will spend next 1 month creating value on my own time." "I am currently on a 3 week family emergency trip." |
4. Volunteer the limits of your own analysis before being asked.
"…and where I think the numbers can't yet support a conclusion."
"…my diagnostic classifier is trained entirely on synthetic cards and has never been scored
against labelled field data."
5. Credentials get one clause, then drop it.
The entire credential is: "I have worked at Occidental for over 5 years and on real-time
production and drilling analytics." No title, no achievements, never "expert" or "specialist".
Competence is carried by knowing what to name — "fillage on plunger stroke, spacing, SPM,
unit balance"; "rod-on-tubing wear, corrosion, scale, solids". The reader infers it.
