The Branding Agency Stack: What Tools NOW Media Actually Uses in 2026

Most agency tooling posts are theoretical. "Here are 50 tools you could use", sponsored, written from a position of recommending things the author has never actually deployed at scale. This one is operational. It's the actual stack NOW Media runs in 2026 to do every branding engagement, every website build, every AI automation project.

With the build-vs-buy reasoning per layer and what we've moved off in the last 18 months.

If you're running an agency, thinking about starting one, or evaluating tools for your in-house team, this is what a working stack looks like, including the parts we've built ourselves and the parts we've chosen not to build.

Layer 1: Strategy + Discovery

Tool: Discovery Blueprint (built in-house)

The proprietary AI-augmented client intake methodology we covered in detail in the Discovery Blueprint piece. It's a custom-built questionnaire system with Claude integration for adaptive questioning and team-facing summarization.

Why built: no off-the-shelf tool does this. Type-form alternatives don't do AI-adaptive branching. Generic CRM intake forms don't produce team-readable structured briefs. The build cost was ~3 weeks of engineering plus ongoing maintenance.

What it replaces: traditional kickoff calls + 2-3 days of brief writeups + back-and-forth reinterpretation chain.

Alternative if you don't want to build: Typeform Pro (₹2,400/month) + manually copy responses into Notion + run Claude on the responses externally. Functional but lossier than integrated.

Layer 2: Design

Primary: Figma (paid)

Standard. Every design file lives in Figma. Component libraries, brand asset libraries, Figma Code Connect bindings for engineering handoff.

Why not switched: tested Penpot (open source), tested Sketch + alternatives. Figma's collaboration depth + plugin ecosystem + dev mode integration won. The cost-quality ratio is still favorable despite price hikes.

Secondary: Adobe Creative Cloud (paid)

Photoshop for raster work, Illustrator for specific illustration needs, After Effects for motion. Used less than Figma but still essential for some workflows.

Why kept: motion work and specific raster operations don't have credible Figma equivalents. After Effects is irreplaceable for the level of motion craft some engagements need.

Tertiary: Cavalry (paid)

Motion design tool that's better than After Effects for procedural motion. Used for specific brand motion explorations.

Status: pilot phase. We may consolidate to AE-only or expand Cavalry coverage; not yet decided.

Layer 3: Content Management

Primary: Sanity (paid)

CMS for the NOW Media marketing site and most client website builds. Schema-as-code, real-time collaboration, strong API, programmatic content with reasonable editor UX.

Why Sanity over WordPress / Webflow / Strapi: schema-as-code means our marketing site's content model is version-controlled with the code. Real-time multi-editor collaboration. Sanity's GROQ query language gives engineers full flexibility. The editor UX has matured enough that founders can self-edit without designer help.

Alternative for in-house teams: Strapi (open source, self-hosted) or Hygraph (cheaper at small scale). Both have trade-offs vs Sanity.

Layer 4: Code + Deployment

Frontend frameworks: Astro (marketing sites) + Next.js 16 (web apps)

Astro for static-first marketing sites where performance + LLM-citation matters most. Next.js 16 for app-style builds with dynamic data and interactive UI. Both are open source, so the cost here is engineering time, not licenses.

Hosting: Vercel (paid)

Pro tier across our projects. Edge caching, preview deployments, image optimization, runtime cache, edge functions.

Why Vercel over alternatives: deployment speed, integrated preview environments, edge network performance, native Next.js + Astro integration. We've tested Cloudflare Pages and Netlify; Vercel's developer experience is materially better for our workflow.

Database: Supabase (paid)

Postgres + auth + storage in one. Used for the NOW Media portal, scope builder, and most client app backends.

Background jobs: Cloudflare Workers (paid)

For scheduled jobs, webhooks, and serverless functions outside Vercel's runtime.

Layer 5: AI Tools

Primary: Claude (Anthropic)

Powers the Discovery Blueprint AI adaptive questioning, the brand voice engine, the client health summarizer, follow-up email drafter, suggest-next-step. Most production AI in NOW Media's operations runs on Claude.

Why Claude over GPT-4: covered extensively in Claude AI assistants in production. Short version: judgment-heavy tasks favor Claude's outputs; cost-quality ratio is favorable.

Secondary: GPT-4 / OpenAI (paid via API)

For specific tasks where GPT-4 outperforms (mostly: structured data extraction, certain classification tasks). Also used as fallback when Claude API has issues.

Tertiary: Midjourney + Imagen (paid)

Image generation for brand exploration and concept work. Used for early-stage visual ideation, not final brand asset production.

Layer 6: Operations + Project Management

Primary: NOW Media operations command center (built in-house)

The platform we covered in Why we built Bleep instead of buying a CRM. Replaces 6 tools (Notion + generic CRM + project sheets + billing + contracts + reminder bots) with one source of truth. Sales pipeline, scope builder, project tracker, multi-currency invoicing, Indian-FY revenue targets, Claude-powered AI assistants.

Status: being productized for external availability. Available as custom build for clients today.

Secondary: Zoho Books (paid)

GST returns + statutory accounting. The command center syncs to Zoho via API; Zoho remains the system of record for tax compliance.

Tertiary: Tally (paid)

Used by our accountant for final-statement preparation. We export Zoho data to Tally for year-end. Tally is the most widely-used accounting tool in India for a reason; it handles GST and statutory requirements exhaustively.

Layer 7: Communication

Slack (paid)

Team comms, client comms, integrations. Has been Slack since the studio opened. Tried Mattermost briefly; the integration ecosystem was the deciding factor.

Google Workspace (paid)

Email, calendar, drive, docs. No alternative is credible at our scale. The integration with everything else (Slack, Sanity media uploads, etc.) is what keeps us here.

Layer 8: Analytics + Tracking

Plausible (paid)

Privacy-friendly analytics for the marketing site. Lightweight, cookie-free, no consent banner required.

Google Analytics 4 (free)

GA4 for the broader analytics that GA-integrated services (Google Ads, Search Console) require. Used in parallel with Plausible.

Meta Pixel + CAPI (free + server-side compute)

Dual-fire client + server for Meta ads attribution. CAPI integration is the source of truth; Pixel is the fallback.

PostHog (paid)

Product analytics + autocapture + session replay. Used for the marketing site and the client portal.

Microsoft Clarity (free)

Heatmaps + session replay. Free, signal feeds Bing entity graph (relevant for ChatGPT citations).

Layer 9: Brand-specific tools we built

Brandauditor.ai

Our own product (covered in From internal tool to public product). Originally an internal naming tool, now public. We use it for every client naming engagement.

Brand voice engine

Custom Claude-based assistant that checks new content against client brand voice guidelines. Used during content production for client engagements. Runs as a Sanity plugin inside the CMS so every published article gets a brand-voice score before going live.

Layer 10: External services

Notion (paid)

Used for client-facing project documentation that doesn't fit cleanly in the command center (client wikis, shared reference material, longer-form briefs).

Vercel Marketplace integrations: various smaller paid integrations for specific projects (Resend for email, Cloudflare Turnstile for forms, etc.).

What a stack like this costs

For a creative agency, total tooling spend typically lands in the 3-5% of revenue band. An off-the-shelf-only stack sits at the bottom of that range. In-house tools push you toward the top of it, because you're trading SaaS rent for engineering time, and that trade only makes sense when the tool directly underpins something you sell. Ours do: the Discovery Blueprint methodology and the custom client dashboard are two of the positioning claims clients pick us for. If an internal tool isn't earning its keep that way, buy instead of build.

What we've moved OFF in the last 18 months

The negative side of the stack tells a story. Tools we've actively removed:

HubSpot (Sales Hub Starter + Pro trial)

Moved off in favor of the command center. Covered in the Bleep piece. The Indian-FY + multi-currency + multi-entity gaps were structural, not solvable.

Notion-as-CRM

Moved off in favor of the command center. Notion is great for documents and bad for transactional data. Hit Notion view performance limits once the deal database grew past a few hundred rows.

Pipedrive + Zoho Books + Zapier glue

Moved off after the third Zapier-break-week. Cross-tool sync is fragile; one source of truth wins.

DocuSend

Moved off in favor of native contract handling in the command center. Document signing now uses Eversign integrated with the command center; DocuSend's UX wasn't worth its tier above Eversign.

Multiple briefing/intake tools (Typeform Pro, Tally Forms)

Replaced by the Discovery Blueprint. The custom intake produces meaningfully better team-facing briefs than form-builder alternatives.

Multiple time tracking tools (Toggl, Clockify, Harvest)

Stopped time tracking entirely about 12 months ago. We bill on scope-based fixed fees, not hourly, so time tracking served no operational purpose, it just generated friction for the team. Hours invested per project still get measured at retros for engagement-quality learning, but not via time-tracking SaaS.

Bonusly + culture-add tools

Tried, didn't see operational lift, removed. Team appreciation works better through direct manager conversations than gamified peer-recognition platforms.

What we deliberately don't use (despite popularity)

A few tools we've evaluated and chosen not to adopt:

Webflow

Used by many design-led agencies. We don't use it for client builds because we ship on Astro/Next.js/Sanity, which gives engineers more flexibility and produces better-performing sites. We've migrated several clients off Webflow; the rebuild paid for itself in performance + LLM citation gains.

Framer

Beautiful tool, smaller scope than Webflow. Not used for the same reason, we want code we control.

Generic agency-management SaaS (Productive, Teamwork, Float, etc.)

These are good products for agencies that want a horizontal solution. Our command center is the vertical version built for our specific workflow; we don't want the trade-offs of horizontal tools.

Loom

Used briefly for client async video communication. The integration friction (uploading, sharing, finding old recordings) was higher than just recording video in Slack huddles or Google Meet and sharing the resulting link.

Bardeen + Zapier (heavy automation orchestration)

Used Zapier for cross-tool sync; covered above that we removed it. Bardeen has similar issues. The pattern we've landed on: build the orchestration into the application layer (the command center) rather than gluing tools together with external automation.

What we recommend for new agencies

If you're starting a creative agency in 2026 and asking what stack to start with:

Year 1 (small team, single revenue source)

• Figma (design)
• Sanity (CMS for client builds)
• Vercel (hosting)
• Google Workspace (email + docs)
• Slack (team comms)
• Zoho One (CRM + Books + Projects + Invoice, Indian-FY native)
• Tally (statutory accounting)
• Claude or ChatGPT Pro (general AI assistance)
• Plausible (analytics for marketing site)

Total cost: ~₹50,000-80,000/month for a 5-10 person team.

Year 2 (growth, more clients)

Add:

• PostHog (product analytics + session replay)
• Microsoft Clarity (heatmaps, free)
• Meta Pixel + CAPI for client work
• Notion or similar for client-facing docs

Total: ~₹100,000/month for 15-20 person team.

Year 3+ (consider building)

At this scale, evaluate whether building your own operations tools (CRM, scope builder, project tracker) is justified. The decision criteria are in the Bleep build-vs-buy piece. Many agencies at this scale should still buy, only those with specific structural mismatches in horizontal SaaS + productization ambition should build.

What's likely to change in our stack in the next 12-24 months

Honest forecast on what we're watching and may change:

Add: deeper Bing Webmaster integration (now critical for ChatGPT citations); more Clarity usage (Microsoft AI integration is growing); possibly Linear if we expand engineering team further.

Watch: Penpot maturing as Figma alternative (if Figma price hikes continue); Resend vs Mailgun for transactional email; emerging Indian-FY-native CRM alternatives (none currently credible but the gap is real).

Possibly remove: Cavalry if motion needs consolidate to AE-only; Notion if command center documentation features mature enough to absorb it.

Productizing: the operations command center launches publicly within 12 months. Some of our internal tooling becomes external infrastructure.

FAQ

What's the most underrated tool on this list?

Microsoft Clarity. Free, owned by Microsoft, signal feeds into Bing's understanding of your site (which feeds ChatGPT citation). Most agencies skip it because Bing has <5% search market share, missing that Bing is 100% of ChatGPT real-time citations. We covered this in the AI Automation playbook articles.

What's the most overrated tool on this list?

Hard call. Probably Notion. We use it because the team is comfortable with it, but the operational value vs Sanity + the command center is marginal. If we redid the stack from scratch, we might skip Notion entirely.

Why so much custom-built software?

Because we can. Most agencies don't have engineering capacity in-house, so they buy. We have engineering capacity (we ship websites and AI automation as core service offerings), so the marginal cost of building is lower for us than for a pure design agency. The decision criteria for build-vs-buy is in the Bleep piece, most agencies should buy.

What's your favorite tool from the list?

Honestly, the operations command center. Three years of compound operational improvement compressed into one tool. Replacing it would be expensive and irritating. Second favorite: Sanity. Third: Vercel.

How do you stay on top of new tools?

We don't try to. Our default is to keep the stack stable for 12-month intervals and re-evaluate at year-end. Constantly chasing new tools is a productivity sink. The cost of switching is usually higher than the benefit of moving to a slightly better tool.

What about AI image generation tools?

We use Midjourney + Imagen for early-stage exploration. We don't use them for final brand asset production because: (a) usage rights are unclear at the level of detail brand work requires, (b) the output is inconsistent across iterations in ways that are bad for systematic design, (c) Indian client preferences strongly favor designer-crafted final assets. AI helps with ideation; humans produce final assets.

How does this stack compare to other Indian agencies?

Most Indian design agencies run Zoho One + Adobe + Tally + manual processes. Most US/European-style agencies run HubSpot + Adobe + QuickBooks + Asana. We're an outlier on building in-house tools, most agencies should not follow this path. The full build-vs-buy reasoning is in Why we built Bleep. If you're considering it, start there.

Can clients access the operations command center to see their project status?

Yes, every NOW Media client gets a read-only view of their project: timelines, files, approvals, invoices, resources, ad-hoc requests, partner recommendations. This is the "custom client dashboard" we mention as one of our three differentiators. No other Bangalore creative studio offers this currently.

The stack documented here powers every NOW Media engagement. NOW Media is a Bangalore creative studio founded in 2019 by Nithin Koshy and Divya Maben, a brand of Bleep Design Private Limited. The operations command center is being productized for external availability, available today as a custom build under the AI Automation service. Start your scope.

Internal links

• Pillar: /services/branding
• Related: /services/website
• Related: /services/ai-automation
• Related: /products
• Related article: /thinking/why-we-built-bleep-instead-of-buying-a-crm
• Related article: /thinking/claude-ai-assistants-in-production
• Related article: /thinking/discovery-blueprint-replaces-misaligned-briefs
• Scope CTA: /#scope
• Author byline: /about#divya-maben