The solo operator
A one-person company with a staff of agents: research, content, follow-ups, and back office.
Scenario
You run a business alone — freelancing, a product, a side hustle next to a day job. The work that actually grows it (outreach, content, follow-ups, research) loses every day to the work that merely keeps it alive (admin, inbox triage, bookkeeping prep). The classic fix is hiring; the Neuralis fix is a staff of agents in one project, working your backlog while you keep the judgment calls.
The team
One project, you as owner, three to four agents:
| Agent | Job | Typical setup |
|---|---|---|
| Assistant | Daily driver: triage, drafting, task tracking, "figure this out" | Your strongest model; full package surface |
| Researcher | Prospect research, competitor watch, market scans | Web research tools + a delegate persona for deep dives |
| Writer | Proposals, posts, newsletters in your voice | Identity files seeded with your tone and past writing |
| Ops | Recurring chores: weekly summaries, follow-up nudges, report prep | Mostly workflow-driven, cheap model |
Each agent keeps its own identity files and rewrites them as it learns your business — the Writer genuinely gets better at sounding like you.
The wiring
- Mount your working folders as sources and sync them: contracts, notes, past proposals become searchable memory the whole team shares.
- Your existing tool folders come along. If you already keep a
.claude/or.cursor/directory of skills and rules, the synced repo contributes them as source packages — your accumulated know-how transfers on day one. - External services attach where you need them: an MCP server on the agent's settings, or a skill whose script calls a public API with a scoped credential — the key lives in the encrypted store, never in a prompt.
- The machine desktop handles everything that only exists as a website: the Assistant logs into your tools once, and the session persists.
The rhythm
Workflows carry the recurring load, visible on the Calendar like a rota:
- Monday 08:00 — Researcher: weekly market and competitor scan into
data://briefs/. - Daily 17:30 — Ops: collect the day's changes and open threads into one evening summary.
- Friday — Writer: newsletter draft from the week's notes, left in chat for your edit.
Every run executes with your rights, records a result summary, and lands as a normal conversation you can open and continue.
Governance
Even solo, the guardrails earn their keep: Balanced permission profile so
risky actions pause for approval; a spend cap per agent (daily, weekly or monthly) so an
experiment never surprises you; the audit log as your own flight recorder.
You are the owner — but the agents are not.
Extend it
Start with the Assistant alone and split roles off as load appears — a new agent is a minute of setup, not a hire. When a workflow proves itself, raise its cadence; when a skill keeps misfiring, fix its text — the team improves as fast as you can describe the job.