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
GTM Engine
Lead sourcing Source leads directly from GitHub, Dev.to, npm, Hacker News, 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. LinkedIn search runs in the browser extension, against your own logged-in session — it is the only source that yields a LinkedIn profile URL, and so the only one that feeds LinkedIn outreach.
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 via Composio OAuth; Swipe One via API key) pushes leads on first contact.
Email sends server-side. LinkedIn is the browser extension — Ozigi for LinkedIn on the Chrome Web Store — which both finds the leads and sends the connection requests, inside your own logged-in tab, because LinkedIn withholds search results and the Connect button from flagged headless sessions. The LinkedIn channel is the connection request with a personalised note; Ozigi does not send LinkedIn DMs.
Content Engine
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. Pick who the piece is for and the engine calibrates jargon, code, analogies, and how claims are evidenced to that reader. Every long-form draft is then audited before you see it — for AI cadence, for code that breaks on paste, and for whether it actually landed on the audience you asked for. Write, schedule, and send email newsletters directly from the dashboard. Manage your subscriber list and track delivery.
Core Systems
The Banned Lexicon
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.
The Structural Audit
The Banned Lexicon blocks the words. This catches everything a word list can't reach. A model routes around a blocklist by picking a synonym, but it can't synonym its way out of thirty paragraphs of identical length, four sentences opening with "You", a question transitioning into every section, or the same point restated in three places. Seventeen detectors run over every long-form draft after generation and return a structural score out of 100 with each flag anchored to a specific span.
The same pass reads every code block for leaked credentials, injectable SQL, and — the one that bites readers most — smart quotes and non-breaking spaces, which are invisible on the page and a syntax error the moment someone pastes the snippet. Those two are hard errors that block publication; style flags are advisory. It also checks the draft against the reader you selected and the content mode you picked, so a beginner tutorial that assumes fluency or a how-to with no steps gets caught before you do. Pure computation, no second model call: ~10ms on a 2,500-word article. Read the deep dive.
System Personas
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.
Gemini 3.1 Flash Image Generation
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.
Human-in-the-Loop (HITL)
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.
Ozigi Copilot
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.
Who Is the Company Behind Ozigi?
-
Seller: Ozigi
-
Year Founded: 2024
-
HQ Location: Marina Bay Area, SG
-
LinkedIn® Page: www.linkedin.com
1 employees on LinkedIn®
