Seerist
Win the work, deliver it, grow the product
For agencies and SaaS companies using freelance platforms as a channel. Seerist finds jobs worth bidding on, scores them against your own ideal-client profile, drafts the proposal in the voice that has been winning, and — after a human clicks Submit — turns the won contract into delivered work. Between contracts it watches the site, the ads, and the attribution. Day to day you talk to named AI employees.
Agency workspace
A services shop bidding as its core revenue model. Speed, fit, and win rate. No product to promote.
SaaS workspace
Freelance platforms as a growth channel. Every bid is designed to win the contract, drive a product signup, or at least put the product in front of someone who needed it.
Four engines, one product
Built together — not staged behind feature gates. Lyvena runs these engines as the services we offer.
A — Bid & Proposal Engine
Jobs arrive from public RSS/JSON feeds (every ten minutes), the Chrome extension on a page you are viewing, forwarded job-alert emails, and platform APIs where approved. Saved searches filter every source through one normalised job shape. AI scores fit against your ideal-client profile with a written reason — never a bare number — then drafts the proposal in the voice that has been winning. You walk a Kanban: New → Scored → Drafted → Needs edits → Approved → Submitted. The extension fills the platform field. You click Submit.
B — Delivery Engine & Studio
A won contract becomes a task DAG, executed through the model gateway behind a mandatory human QA gate. Studio is the IDE: you describe the work; it plans files, writes them whole, previews them, and can run npm install, a real build, and a real test suite in a sandbox. Default stacks are InstantDB for real-time apps and InsForge for fuller backends — never forced over a client’s own stack. Nothing is marked delivered until a person approves every task.
C — Growth Engine
Between contracts, Seerist watches the site, drafts ads and pages, and attributes signups from bids, ads, and the site through one model. Site studio reconstructs the live design system. Visitor intent is first-party only — pages, referrer, campaign, dwell time — with a consent gate. Playbooks are reusable strategies (SEO/AEO, competitor-migration bids, post-win attribution). Nothing the Growth Engine produces is auto-published.
D — AI Employees
Day to day you talk to a roster, not a button. Seven built-in roles plus anyone you hire, each a threaded conversation over one reasoning layer, a step cap, an approval gate, and a full audit trail. A hired employee is a name, a face, and a toolkit over one of those seven roles — naming someone “The CEO” grants nothing extra.
How jobs come in
Four intake paths. One filter engine. A rule means the same thing on a marketplace, a job board, and a careers page.
Public feeds
RSS, Atom, and JSON polled every ten minutes. No login. No HTML scrape.
Chrome extension
Capture the job page you are already viewing. Autofill an approved draft. You click Submit.
Email alerts
Forward the job emails the platform already sends. Same pipeline as everything else.
Platform APIs
Code-complete per platform. Fail closed until that marketplace’s developer access is approved.
Studio
Studio is a conversation that writes real files
You say what you want. Studio decides whether that was a change, a command, or a question — and only then acts. Most messages are routed without a model call at all.
edit / build
Plans the files and writes them whole.
run
npm install, a real build, a real test suite, in a container.
explain
Answers and writes nothing, in a branch that cannot write.
Your AI workforce
Seven built-in roles. Hire more over those roles. Talk to them. Every turn is audited.
The Scout
Captures jobs and scores fit across connected platforms.
The Drafter
Writes proposals and applies per-platform product-mention policy.
The Builder
Turns won contracts into delivered work in Studio and the task DAG.
The Closer
Drafts post-win client comms and scheduling. Does not send unless you do.
The Grower
Site, ads, visitor intent, and bid→signup attribution — SaaS workspaces.
The PM
Reads a coded evidence pack. Writes a roadmap only when there is enough signal. Has no authority.
The CEO
Org-level orchestration. Money, contracts, deletion, and outbound comms wait in an approval queue.
Not settings. Not v1 limits.
These hold in code and in tests. They are why Lyvena can offer these services without gambling your marketplace accounts.
You click Submit
Nothing is ever submitted to a freelance platform by Seerist. The extension fills the platform’s own field. A scripted click on your session is what gets accounts permanently banned — so there is no such click in the product.
The CEO cannot spend or bind you
Money, contracts, deletion, and outbound communication wait for a person. An unrecognised action class falls into the gate, never through it. There is an org-level kill switch.
Growth stays a draft
Pages, ad creative, and deploy-sync copy land as drafts. “Published” only records that a human shipped it elsewhere.
Visitor intent is first-party
No identity graph, no IP-to-company lookup. Tracking stays off until a jurisdiction and a live privacy-policy URL are set. Denied consent is never stored.
Want Lyvena to run Seerist with you?
We use this product to win work, deliver it, and grow yours. Book a call, or open the app and start a workspace.