NetBramha Studios · Internal Platform
The Voice
A brief goes in. A finished post comes out — in the studio's actual voice. LinkedIn, Behance, Instagram, reels, case studies, engagement. One tool, every format.
Live
netbramha-voice.netlify.app
Cloudflare Worker · KV Storage
Google OAuth · @netbramha.com
The Problem
The studio's voice lived in one person's head.
NetBramha has a recognisable way of writing — reflective openers, a specific values turn, a founder voice for case studies, eight hard rules for engagement comments. None of it was written down. Every post took a senior person, a blank page, and enough time to remember how the last one was phrased.
01Unwritten rules, inconsistent output
People knew when something sounded wrong but couldn't say why. The brand voice existed in practice but not in a form anyone could hand off, train on, or scale.
02Every format from scratch
A People & Perspectives post, a Behance board, an Aashish case study, an engagement comment on a prospect's LinkedIn — four different shapes, four different registers, no starting point.
How It Works
Name the project. Describe what happened. Get the post.
01
Create a project
Give it a name and pick a type from the grouped dropdown — LinkedIn post, reel script, Behance board, case study, engagement comment, or content ideation. The input label and platform controls adjust to match.
02
Paste a brief or a URL
For posts: raw notes. For case studies: a few data points. For Behance: paste a netbramha.com/work URL and the tool fetches the source itself. For engagement: paste the post you're replying to.
03
Auto-detect routes the brief
A fast Haiku call classifies the type before the main generation fires. The result shows a stamp — Detected or Forced — so nothing goes out as a black box. Wrong route? One click to override and re-run.
04
Choose from 3 options, save, export
Posts return three genuinely different takes as Option 1 / 2 / 3 tabs. Pick one, copy it, or save the project. Every saved project is shared across the team — visible in the Projects pane, exportable to Excel individually or in bulk.
What It Generates
Seven routes. Three voice guides. One tool.
Each route loads only its own voice skill — the tool can't produce anything outside these formats.
NetBramha Page
4 post types
  • People & Perspectives
  • Culture / studio moment
  • This Week in Design
  • Hiring / DILO / event recap
Aashish (Founder)
2 post types
  • Client case study (THE PROJECT / OUTCOME / WHY / HOW / INTERESTING PARTS)
  • Founder hiring post
Reels & Video
Full script kit
  • 3 hook options
  • 60s spoken script
  • On-screen text overlays
  • Platform caption + shot notes
Case Studies
Behance full board
  • Hero · Mission · 3 Pillars
  • Results · Challenge · Decisions/IA
  • Feature highlights · Design system
  • Business lessons
Case Studies
Website copy
  • Title · Context · Goal · Outcomes
  • Section highlights (2-word tag, 6-word line)
  • The Results · Process captions
Engagement + Ideas
2 utility modes
  • Engagement comment (never mentions NB, never generic)
  • Content ideation — posts, reels, carousels, campaigns
The voice isn't a style guide in a Notion doc. It's a machine you brief — and it answers in the studio's register, not a plausible imitation of it.
— THE CORE PREMISE
What Makes This Different
Five decisions worth explaining.
Skills, not prompts
Each voice — page, Aashish, engagement, reel, channel, case study — lives in its own versioned SKILL.md. The tool is only as good as the skill behind the route. When the voice drifts, you edit the skill file, rebuild, redeploy. Nothing else changes.
Classification before generation
Auto-detect is a separate Haiku call that fires before the main generation. The route label shows in a stamp so you can catch a misclassification before reading the output — and override it in one click without re-entering the brief.
Behance fetches the source itself
Paste a netbramha.com/work URL and the Cloudflare Worker fetches the page server-side, strips it to readable text, and passes it to the model. No copy-pasting a 3,000-word case study by hand. Locked to netbramha.com so it can't be misused.
The "never invent" rule
Every generation directive carries an explicit instruction: never fabricate metrics, client names, or facts not in the brief. A case study without a number gets a qualitative heading, not a made-up stat. For a tool representing the company, that's non-negotiable.
Shared project library
Saved projects land in a shared KV store — every @netbramha.com user sees the same library. Multi-select export lets you pull a single project or the entire library into a structured Excel sheet: one row per content piece, columns for type, variant, author, date, content, and inputs.
At a Glance
9
Content routes across LinkedIn, Behance, reels, and case studies
6
Voice skills — each versioned, editable, independently deployable
3
Options returned per post — genuinely different angles, not near-copies
0
Invented metrics ever allowed through to a saved or exported project
Stack
Single-file HTML
Cloudflare Worker
Cloudflare KV
Claude Opus 4.8 / Haiku 4.5
Anthropic API
SheetJS (xlsx export)
Google OAuth · @netbramha.com
Netlify
No build step
The studio's voice — written down, wired up, and always on.
NetBramha Studios
Internal Tooling · 2025