Can Omentir be vibe coded?
Finds ICP-fit LinkedIn buyers, sends human-paced outreach, and files replies in one inbox
The personal loop is buildable in a sitting: score a list you already have, draft connection notes, queue sends, stop on replies. Live LinkedIn send is Unipile, a paid API, not a trivial key, and LinkedIn will still restrict a real account if you ignore the caps. The hosted product's own repo is already MIT with Docker Compose, so the interesting move is clone-and-run, not a from-scratch rebuild. That fork still needs Firebase, Unipile, and Gemini, which is ops. Keep paying if you want them to run those three, plus the three-bookings-a-week refund.
Jump to the build brief ↓Legacy-calibrated assessment
Checked Aug 2026
What you pay today, before any DIY hosting
medium editorial confidence
Tracked separately from the pricing check
Buildability by layer
Screens, forms, and focused interactions
The repeatable job the product performs
Availability and legality of required data
Uptime, queues, support, and maintenance
Security, compliance, and user confidence
The achievable core
- Import LinkedIn profile URLs you already have, score them against an ICP, draft connection notes and follow-ups, send through Unipile or by hand, and stop the sequence when a reply lands.
- Track contacts, sequence outreach, and log replies for a pipeline you own.
- A responsive interface with real empty, loading, success, and error states.
The parts a prompt cannot buy
- the three-bookings-a-week refund on the hosted plan
- someone else paying for and babysitting Unipile, Firebase, and Gemini
- daily invite caps already wired, so you do not have to invent account-safety defaults
- MCP and the Agent API already pointed at a running workspace
- Connectors, OAuth flows, and vendor API changes require constant upkeep.
- The last 20 percent is sync, migration fidelity, speed, and edge cases.
Build, switch, or keep paying
Narrower, with trade-offs
Import LinkedIn profile URLs you already have, score them against an ICP, draft connection notes and follow-ups, send through Unipile or by hand, and stop the sequence when a reply lands.
Use the build brief ↓No checked option yet
Compare the prior art below or build only the workflow you need.
$49/mo
They pay $49 so they do not have to stand up Unipile, Firebase, and Gemini, and so a missed week of bookings can be refunded. The MIT repo is the same app; self-hosting just moves the vendor invoices onto you.
Visit Omentir ↗Why people still pay
They pay $49 so they do not have to stand up Unipile, Firebase, and Gemini, and so a missed week of bookings can be refunded. The MIT repo is the same app; self-hosting just moves the vendor invoices onto you.
Connectors, OAuth flows, and vendor API changes require constant upkeep.
The last 20 percent is sync, migration fidelity, speed, and edge cases.
The brief
Context, requirements, acceptance criteria, non-goals, and the full production standard — as Markdown, ready for any coding agent.
Build brief — a focused alternative to Omentir
Context
Omentir — Finds ICP-fit LinkedIn buyers, sends human-paced outreach, and files replies in one inbox. It currently costs $49/mo.
The personal loop is buildable in a sitting: score a list you already have, draft connection notes, queue sends, stop on replies. Live LinkedIn send is Unipile, a paid API, not a trivial key, and LinkedIn will still restrict a real account if you ignore the caps. The hosted product's own repo is already MIT with Docker Compose, so the interesting move is clone-and-run, not a from-scratch rebuild. That fork still needs Firebase, Unipile, and Gemini, which is ops. Keep paying if you want them to run those three, plus the three-bookings-a-week refund.
This brief describes a focused, single-operator replacement for the part of Omentir that is genuinely reproducible. It is deliberately narrower than the product it replaces, and it says so in writing. Build the useful core; do not pretend to have rebuilt the rest.
What you are building
Import LinkedIn profile URLs you already have, score them against an ICP, draft connection notes and follow-ups, send through Unipile or by hand, and stop the sequence when a reply lands.
Track contacts, sequence outreach, and log replies for a pipeline you own.
A responsive interface with real empty, loading, success, and error states.
Requirements
Functional
CSV of LinkedIn profile URLs you already have.
Optional Unipile account with one LinkedIn account connected.
Node with SQLite (better-sqlite3).
Data and integrations
OpenAI, Anthropic, or Gemini API key.
Each of these needs a real account, credential, or quota. Set them up before writing feature code.
Non-functional
Accessibility: semantic markup, labelled controls, visible focus, and reduced-motion support.
Security: server-side secrets, validated input, and no credentials in the client bundle.
Reliability: retries with backoff on external calls, and a clear failure state when a provider is down.
Portability: the operator can export their data and leave without losing it.
Implementation brief
Build me a personal LinkedIn outreach workspace to replace Omentir. Requirements:
Local Node + TypeScript: Express on localhost:3000, better-sqlite3 for storage,
node-cron for send windows. No frontend framework.
I define my product and ICP once in product.yaml: what I sell, titles, company
sizes, geos, and disqualifiers.
Import prospects from a CSV of LinkedIn profile URLs I already have. Store
name, title, company, profile URL, score, status, and last action.
Score each prospect 0-100 against the ICP in one LLM call (key in .env) with a
two-line reason. Under 70 stays in a review pile and is never contacted.
Draft a connection note under 300 characters plus two follow-ups from the
profile and my product.yaml. Drafts wait in an approval queue until I click Send.
Optional send path: if UNIPILE_DSN and UNIPILE_API_KEY are in .env, send through
unipile-node-sdk from one connected LinkedIn account at 20 invites and 40
messages per day, randomized gaps in business hours. If those keys are missing,
copy the approved text to the clipboard so I can send it myself.
Poll replies every 15 minutes when Unipile is configured, or let me paste a
reply in by hand. Stop the sequence the moment one lands. Dashboard lists
prospect, score, status, and thread.
No accounts, no telemetry, everything on my machine except the LLM and optional
Unipile calls. Secrets in .env.
Out of scope: scraping LinkedIn, a contact database, a booking guarantee, and
a hosted MCP control plane. Do not send except through Unipile or my clipboard.
README: CSV columns, .env keys, how to connect one LinkedIn account in Unipile,
and a warning that per-account limits are real, so keep the caps low for the
first two weeks.
Delivery standard
Inspect the repository first, then write a short implementation plan before writing code.
Deliver the smallest complete end-to-end workflow first; every primary control must work against persisted data.
Use real validation and storage; never substitute fake dashboards, decorative controls, hard-coded success states, or mock integrations.
Include responsive layouts plus genuine empty, loading, success, validation, and failure states.
Keep secrets server-side in environment variables, provide .env.example, and never commit credentials or user data.
Add structured logs around every external call and return actionable errors without leaking sensitive details.
Write unit tests for the core logic and one automated test of the main user journey.
Finish with a README covering setup, architecture, data location, backups, tests, deployment, and known limitations.
Acceptance criteria
A clean install starts the app using only the README and .env.example.
The primary journey works from first visit through saved result, reload, edit, export, and deletion where applicable.
Invalid input, missing configuration, provider failure, and an empty database each have a usable state.
The interface works at 390px and 1440px, is keyboard navigable, and shows visible focus on every control.
Tests, type checking, linting, and a production build all pass with no ignored failures.
No part of the interface implies a live integration, security guarantee, or scale capability that was not actually built and verified.
Non-goals
Do not build these, and do not claim to have replaced them:
The three-bookings-a-week refund on the hosted plan.
Someone else paying for and babysitting Unipile, Firebase, and Gemini.
Daily invite caps already wired, so you do not have to invent account-safety defaults.
MCP and the Agent API already pointed at a running workspace.
A support line when a sending account gets restricted.
What you still own after launch
Secure credentials, rotate secrets, and handle provider rate limits.
Run migrations, backups, restores, and dependency updates.
Test the critical journey after every model, API, or hosting change.
Monitor failures and fix the edge cases a first prompt will miss.
Maintain every third-party integration as APIs and OAuth rules change.
Risk
Operational risk. The code is achievable; dependable data, integrations, and ongoing operations are the real cost.
Editorial confidence in this assessment: medium. No reviewed project implementation is linked yet.
Prior art
Working open-source software you can read, fork, or borrow from before starting:
Omentir (MIT repo) — the hosted product's own source; Docker Compose, still needs Unipile, Firebase, and Gemini
Unipile — the LinkedIn send/receive API the hosted product and any honest DIY build both rent
n8n — self-hostable workflow glue if you would rather wire ICP scoring to a send step than write a dashboard
Generated by Can It Be Vibe Coded? · Full report: https://www.canitbevibecoded.com/omentir
You still own the product
- Secure credentials, rotate secrets, and handle provider rate limits.
- Run migrations, backups, restores, and dependency updates.
- Test the critical journey after every model, API, or hosting change.
- Monitor failures and fix the edge cases a first prompt will miss.
- Maintain every third-party integration as APIs and OAuth rules change.
Projects built from this idea
No reviewed implementation has been linked for Omentir yet. A submission is evidence for review, not automatic proof that the whole product was replaced.
Built a version of Omentir?Submit the project as evidence for this report.
Open-source prior art
the hosted product's own source; Docker Compose, still needs Unipile, Firebase, and Gemini
View project ↗Unipilethe LinkedIn send/receive API the hosted product and any honest DIY build both rent
View project ↗n8nself-hostable workflow glue if you would rather wire ICP scoring to a send step than write a dashboard
View project ↗Before you start
Can Omentir be vibe coded?
Partly, if you narrow it. The personal loop is buildable in a sitting: score a list you already have, draft connection notes, queue sends, stop on replies. Live LinkedIn send is Unipile, a paid API, not a trivial key, and LinkedIn will still restrict a real account if you ignore the caps. The hosted product's own repo is already MIT with Docker Compose, so the interesting move is clone-and-run, not a from-scratch rebuild. That fork still needs Firebase, Unipile, and Gemini, which is ops. Keep paying if you want them to run those three, plus the three-bookings-a-week refund.
What can an AI coding agent reproduce from Omentir?
Import LinkedIn profile URLs you already have, score them against an ICP, draft connection notes and follow-ups, send through Unipile or by hand, and stop the sequence when a reply lands. Track contacts, sequence outreach, and log replies for a pipeline you own. A responsive interface with real empty, loading, success, and error states.
What will a DIY Omentir replacement still be missing?
the three-bookings-a-week refund on the hosted plan; someone else paying for and babysitting Unipile, Firebase, and Gemini; daily invite caps already wired, so you do not have to invent account-safety defaults; MCP and the Agent API already pointed at a running workspace; Connectors, OAuth flows, and vendor API changes require constant upkeep.; The last 20 percent is sync, migration fidelity, speed, and edge cases.
What do I still own after building a Omentir alternative?
Secure credentials, rotate secrets, and handle provider rate limits. Run migrations, backups, restores, and dependency updates. Test the critical journey after every model, API, or hosting change. Monitor failures and fix the edge cases a first prompt will miss. Maintain every third-party integration as APIs and OAuth rules change.