What Mani Doesn't Do (And Why)

Every feature request we say no to makes the product better. That sounds like a platitude but I mean it literally. Every feature we add increases complexity, increases the surface area for bugs, and dilutes the focus of the product. The features we choose NOT to build are as important as the features we ship.

Here is the honest list of things mani does not do, why we chose not to build them, and what we recommend instead.

Mani is not a CRM

Mani does not manage your customer relationships, track your pipeline, score your leads, or send automated follow-up sequences. Every month, someone asks me to add "just a simple CRM" to mani. There is no such thing as a simple CRM. The moment you add contact management, you need segmentation. The moment you add segmentation, you need tagging. The moment you add tagging, you need automation. And now you have rebuilt HubSpot poorly.

Use HubSpot, Pipedrive, or Close for CRM. Mani integrates with them through ad-to-CRM attribution. Your ad creative lives in mani. Your customer data lives in your CRM. Each tool is excellent at its job. Merging them would make both worse.

Mani is not an analytics tool

Mani does not track your ad performance, calculate your ROAS, or build attribution models. We will never build a dashboard that shows you which ads converted because that job is done better by tools with direct access to platform APIs: Triple Whale, Northbeam, or the platform-native analytics in Meta and TikTok.

What mani does instead: when you approve or reject ads from the daily queue, we learn your preferences. When you mark an ad as "top performer" after seeing its results, we bias future generations toward that style. This is preference learning, not analytics. The distinction matters. Analytics tells you what happened. Preference learning shapes what happens next.

Mani is not a video editor

Mani generates video storyboards, scene plans, and frame-by-frame visual direction. But it does not edit video footage. It does not add transitions, trim clips, adjust audio levels, or export timeline sequences. CapCut, DaVinci Resolve, and Adobe Premiere are video editors. Mani is a video concept generator.

The workflow is complementary: mani generates the concept (script, shot list, visual direction, text overlay specifications). You or your team record the footage. CapCut or your editor of choice handles the assembly. Trying to build a video editor inside mani would triple the codebase complexity for a job that CapCut already does for free.

Mani is not a social media scheduler

Mani does not schedule your posts for optimal times, manage your content calendar across platforms, or provide a unified inbox for comments and DMs. Buffer, Later, and Hootsuite handle scheduling. Mani handles creation.

The export flow is designed for this handoff: generate ads in mani, approve the ones you like, export to your scheduling tool, and schedule from there. We built direct export to Meta, TikTok, LinkedIn, and X (via API), but the scheduling and calendar management is deliberately outside our scope. Adding a scheduler would mean competing with 20 established tools on a feature that is a commodity. We would rather be excellent at one thing (generation) than mediocre at two things.

Mani is not a landing page builder

Some AI ad tools try to generate both the ad AND the landing page. We chose not to. Landing pages require form builders, A/B testing infrastructure, analytics integration, and responsive layout engines. These are complex, mature product categories where Unbounce, Webflow, and Shopify's built-in pages are already excellent.

Mani generates ads that link to your existing landing pages. Your landing page builder handles the conversion optimization. This separation means you can use whatever landing page tool your team is already proficient with. You do not need to learn a new page builder just to use mani.

Mani is not an SEO tool

Mani generates creative for paid and organic social media. It does not generate blog posts, optimize meta tags, build backlink profiles, or track keyword rankings. Ahrefs, SEMrush, and Surfer SEO are SEO tools. Mani is a creative generation tool.

There is a growing category of "AI content for SEO" tools. I have opinions about most of them (the content they generate ranks but does not convert because it reads like AI wrote it). If you need SEO content, hire a writer who knows your industry. If you need ad creative, use mani. Different jobs, different tools.

Mani is not a design system tool

Mani does not manage your brand guidelines, store your logo variations, enforce your typography rules, or provide a shared component library for your design team. Figma, Frontify, and Brandfolder handle design system management.

Mani READS your brand (via the Brand DNA scan) but does not WRITE or MANAGE it. Your brand identity is an input to mani, not an output. If your brand identity changes (new colors, new tone, new positioning), you re-scan your URL and mani updates its understanding. But the source of truth for your brand lives in your design system, not in mani.

Mani is not a customer data platform

Mani does not collect first-party customer data, build audience segments, or create lookalike audiences. Segment, mParticle, and the platform-native audience tools handle customer data. Mani generates the creative that targets those audiences, but the targeting intelligence lives in your ad platform, not in ours.

This is a deliberate privacy decision as much as a product scope decision. The less customer data we hold, the smaller our attack surface, the simpler our compliance posture, and the fewer data-breach scenarios we need to worry about. Your customer data stays in tools designed to protect it. We just make the ads.

The philosophy behind the exclusions

There is a temptation in product building to say yes to everything. "Just add a simple X" is the most dangerous sentence in software. Every "simple" addition creates maintenance burden, increases cognitive load for the user, and dilutes the core value proposition.

Mani does one thing: generate brand-consistent ad creative at volume. Every feature we build serves that one thing. Brand DNA extraction serves it (better grounding = better ads). The daily queue serves it (consistent creative velocity). Multi-brand support serves it (same generation, more brands). Platform export serves it (getting ads from generation to publication).

Everything else is someone else's job. And they do their jobs better than we would. The best product is the one that knows its boundaries.