Nimu Beta Is Now Live

Today, we are opening the beta of Nimu.

Nimu is an AI go-to-market workspace for small teams that need to find customers without assembling a stack of disconnected tools. You describe the product, the audience, and the outcome you want. Nimu helps research the market, find prospects, build campaigns, create pages, publish content, and measure what happens next.

The beta is not the finished version of that idea. It is the first version where the core workflows are connected well enough to use as one system.

---

Why We Built Nimu

Most go-to-market software improves one step by creating another handoff.

A prospecting tool finds a person, then asks you to export a CSV. An enrichment tool fills in the email, then sends the row somewhere else. A writing tool drafts copy without knowing what the campaign has already learned. A sending tool reports opens and clicks, but cannot change the landing page or social post that created the demand.

The individual tools may work. The seams become the job.

That is manageable for a large team with dedicated operators. It is a bad trade for a founder, an early growth hire, or a small agency trying to learn quickly. They spend time moving context between systems while every system claims to save time.

Nimu starts from a different unit of work. The unit is not an email, a lead, or a post. It is a goal.

What You Can Do in the Beta

The beta brings the main go-to-market workflows into one workspace.

Find and Prepare Prospects

Search for people by role, company, seniority, or market criteria. Save the relevant prospects, find verified work emails through managed enrichment, and generate a grounded opening line from the facts available for each lead.

Nimu keeps the source record, enrichment result, list membership, and campaign context together. There is no export step between finding someone and preparing the outreach.

Build and Send Email Campaigns

Ask the agent to generate a multi-step campaign from a prompt, review the subjects and messages, choose a list and sending connection, then approve the build.

Campaigns support wait steps, send windows, personalization, open and click tracking, unsubscribe handling, and automatic stops after bounces or replies where reply tracking is available. Broadcasts cover one-time announcements that do not need a sequence.

Sending runs through your own Gmail account or verified domain. Domain checks, mailbox limits, bounce handling, complaint monitoring, and gradual sending controls are built into the workflow because campaign generation is not useful if the sending infrastructure damages the domain behind it.

Create Landing Pages

Describe the page you need and generate a hosted landing page with copy, structure, and styling informed by the workspace profile and brand colors. Edit it through the same conversation, add an optional lead form, and publish it to a stable Nimu page URL.

Views and submissions return to the workspace, so the page is part of the campaign rather than an isolated asset.

Publish to LinkedIn and X

Connect a LinkedIn or X account, draft a post, generate a supporting image, and publish immediately or schedule it for later. Scheduled posts are processed in the background and retain a result for each connected account.

The beta focuses on publishing and scheduling. Full engagement analytics and autonomous content calendars are still ahead.

Understand Search Visibility

Connect Google Search Console and Google Analytics to see search queries, pages, clicks, impressions, index coverage, and search traffic that converts. Run page audits for technical readiness, content structure, performance, and answer-engine visibility.

Nimu can turn audit findings into a concrete development prompt or apply supported fixes to a hosted landing page. It does not pretend that every SEO issue can be repaired automatically.

Review Google Ads Performance

Connect Google Ads to bring account and campaign performance into the same dashboard and agent conversation. The current integration is read-only. Nimu can summarize impressions, clicks, conversions, cost, click-through rate, and average cost per click, but it will not create or modify campaigns during the beta.

How the Agent Works

The agent is the connective layer across these workflows. It can search the workspace, create and edit records, generate content, open the right dashboard view, and carry a task from an instruction to a reviewable result.

Actions with cost or external impact show a confirmation before they run. The confirmation explains what will happen and how many credits it will use. Teams that want a faster loop can enable auto-approve, but the same permissions, validation, and safety checks still apply underneath.

This is an important boundary for the beta. Nimu can do work, not only describe it, but execution should remain visible. An autonomous system that cannot explain what it changed is just another seam with better copy.

What Beta Means

Beta means the product is ready for real work and still expected to change.

Some workflows are deeper than others. Email, prospecting, landing pages, scheduled social publishing, and organic search have working execution paths. Google Ads is reporting-only. Cross-channel planning and optimization are not yet the single continuous loop we want them to become. Some integrations will require more setup than they should.

The purpose of opening now is to learn where the connected workflow breaks under real goals. Not whether a button works in isolation, but whether someone can begin with "find our first twenty customers" and move through research, outreach, content, and measurement without rebuilding context at every step.

Feedback during the beta will shape the order of work. The most useful reports are specific: what you tried to accomplish, where the system lost context, which step still required another tool, and what you expected Nimu to do next.

How Pricing Works

Exploring the workspace, connecting accounts, building campaigns, chatting with the agent, and drafting content do not consume credits. Actions with direct execution cost, such as verified-email discovery, enrichment, sending, image generation, and publishing, use credits.

The one-time Intro pack includes 100 credits for $10. Monthly Growth and Traction subscriptions include larger credit grants with two-month rollover. Every product feature is available without a feature-gated plan; the plans change the amount of execution included, not which screens unlock.

This model keeps the beta usable before a subscription while tying cost to work the system actually performs.

What Comes Next

The immediate work is making Nimu more plan-aware.

Today, the agent can execute across the product. The next step is a durable go-to-market plan that remembers the goal, coordinates channels, records every action, and evaluates results against the same target over time. That includes better reply classification, campaign optimization, social performance, unified reporting, and a clearer approval queue.

The roadmap will also be shaped by what beta users need in real workflows. That may mean publishing to more social and community platforms, supporting additional outreach channels, or taking an existing integration deeper before adding the next one. We will prioritize the places where users already find and speak with customers, not chase the longest integration list.

The product is the ability to give the system a goal, understand what it plans to do, approve the work, and see what changed because of it. More platforms matter when they make that loop more useful.

Try the Beta

The Nimu beta is open. Join today and help decide what we build next.

Create a workspace, add the product website, and give the agent one real goal. Then tell us which workflow still needs another tool, which platform you want to publish to, or which outreach channel Nimu should support next. The beta will be shaped by what users need after that first prompt.