4
What is Ozigi?
Ozigi is a go-to-market engine for founders, DevRel teams, and small technical teams. It handles the four jobs that fill pipeline: finding the right people, qualifying them against your ICP, reaching them with outreach that sounds human, and publishing the content that warms the market before the ask lands.
The two engines share one brain. The same persona voice that writes your LinkedIn sequence also writes your blog post. The same Banned Lexicon that keeps your cold email off the spam filter keeps your newsletter from sounding like it was generated. You define your voice once; it applies everywhere.
The Two Engines
Lead sourcing Source leads directly from GitHub, Dev.to, and LinkedIn based on an ICP you define once. For GitHub, the engine runs a bio-keyword + language + location query against the GitHub user search API and extracts matching profiles. When a profile hides its email, the engine recovers a real address from the user's public commit history. For Dev.to, it pulls authors by tag. For LinkedIn, it searches against your own session.
ICP scoring Every sourced lead is scored by Gemini against your ICP on a 0.0–1.0 scale. Only leads above your threshold enter the sequence. This keeps your sending lists clean and your reply rates high without manual filtering.
Email + LinkedIn sequences Campaigns run multi-step sequences from your own accounts with delays you control. Per-channel daily limits protect your domain reputation and LinkedIn standing. Reply detection pauses a sequence the moment someone responds on either channel. CRM sync (HubSpot, Zoho, Salesforce) pushes leads on first contact via Composio.
Drop in a URL, paste raw notes, or upload a PDF or image. Ozigi extracts the core narrative and returns polished, platform-specific drafts for X (Twitter), LinkedIn, Discord, Slack, and email newsletters — all in your voice, with the Banned Lexicon applied.
Generate full blog posts, tutorials, and technical documentation in MDX-ready format from the long-form module. Write, schedule, and send email newsletters directly from the dashboard. Manage your subscriber list and track delivery.
Core Systems
The single most important reason Ozigi doesn't sound like AI. A hard-coded blocklist enforced at the API route level — not filtered after generation, blocked during it. No "delve", no "robust", no "seamlessly", no "tapestry", no "game-changing". The model is penalised for AI-speak vocabulary, which forces every sentence to be constructed from your actual content. Applied identically to cold email, blog posts, LinkedIn posts, and newsletter copy.
Define who is writing — role, tone, beliefs, things they would never say — and save it once. Every campaign generation, every outreach step, and every content piece applies that persona automatically. One setup, consistent voice forever, across both engines.
Generate platform-aware graphics directly inside the engine. Blank field = abstract background matched to the post topic. Add a graphic title = rendered text graphic with clean typography. Generated images upload server-side to Cloudflare R2 storage and return a public CDN URL — no browser CORS issues, no extra pipeline.
Ozigi handles the 90% — extraction, structure, constraints, platform formatting. You own the 10% — the specific detail, the insider context, the judgment call only a human can make. Every generated campaign includes an Edit step before it goes anywhere.
A context-aware AI assistant built into the dashboard. Copilot has access to your current campaign context, your personas, and optionally the web. It handles ideation, draft refinement, outreach critique, and persona development.
Built with