● Mithil Chureetur / Brand GuideReturn to Portfolio →

Clear. Capable. Commercially aware.

This guide keeps the portfolio consistent when content is updated. The brand should feel like a modern enterprise product: assured, structured and technically credible without becoming cold or over-engineered.

Positioning

Primary: Technical Project, Programme and Product Manager across AI, cloud, data, infrastructure, security and Web3.

Differentiator: A distinctive combination of technical expertise, product judgement and go-to-market experience—bringing delivery discipline, customer understanding and adoption thinking to complex initiatives.

Audience

  • Recruiters and executive search
  • Heads of Delivery, Product and Technology
  • Founders and Web3 infrastructure leaders
  • Cloud, AI and data consultancies

Voice & Capitalisation

Direct, calm and evidence-led. Use active verbs: led, coordinated, scoped, aligned, validated, shipped. Interface labels use ALL CAPS; named roles, capabilities and project titles use Title Case; full-sentence headings and body copy use sentence case. In labels, use AI, Cloud, Data, Infrastructure, Security & Web3. In sentences, use AI, cloud, data, infrastructure, security and Web3. Preserve official forms such as GitHub, GitLab, Jira, Confluence, BigQuery, Pub/Sub, Looker, stakeFi, UI/UX and LLMs.

Message Hierarchy

  1. Product + Technical PM positioning
  2. Full delivery lifecycle ownership
  3. Flagship BCW evidence
  4. Complete expandable capability and project records
  5. Amala product foundation
  6. Product marketing, branding and partnership foundation
  7. Credentials and recruiter fit

Colour system

Ink
#101310
Signal lime
#D9FF52
Product blue
#6F8CFF
Data aqua
#83E9D2
Editing the language: the visible copy is written directly in dist/index.html. The safest workflow is to send the exact sentence or section you want changed and the replacement wording; the published site can then be updated without disturbing the design.

Do

  • Lead with outcomes and delivery responsibility.
  • Use client names consistently.
  • Keep early-career roles concise.
  • Link claims to a specific project or role.

Avoid

  • Claiming engineering work as personal implementation.
  • Unverifiable superlatives.
  • Dense technology lists without context.
  • Confidential architecture, pricing or client information.