One person running the whole loop.

What does one person running the whole loop actually mean?

It means the same human searches, diagnoses, builds the DEMO, approves the send, takes the meeting, deploys, and opens Steward. There is no AE to blame and no designer to ping at 9pm. The product does not split. The calendar does.

Team pages lead with a fear. Size pages lead with how many people are looking at Nova. You should read Solo marketers if the wasted week is the thing that keeps you up. Stay here if you need the seat story for yourself or for a partner who asks why you do not need three tools and two hires. Small team is the next frame when a contractor appears. Agency pages are the isolation frame when a second legal brand appears. The modules do not shrink between those sentences.

Nerxus One does not ship a lite loop for one seat. Scout still never contacts. Radar still models with assumptions. Forge still DEMOs before DEPLOY. Relay still waits on ComplianceGate. Echo still cannot gate. Voice still cannot go cold. Nova still routes nine specialists and comes back last. Steward still keeps health as Healthy, Watch, or At-risk. Overnight dispatch is still not a production claim. One seat does not unsay any of that.

What changes is collision. There is none. What also changes is cover. There is none. A bad send is your domain. A mixed portal cannot happen unless you paste the wrong link. A skipped diagnostic is you being impatient.

Why is there no lite version of Find, Prove, Win, Build, and Run?

A lite version would be a list tool. You already know those. The loop is the reason this product exists. Cutting Build or Run to make a one-seat SKU would put you back in the four-tab week this company is trying to end.

You can ignore Muse for a month. You can ignore market intelligence until preview is on. You can ignore inbound voice if you do not sell it. Ignoring is not the same as the vendor removing the module so the homepage looks simpler.

Credits and meters, when they exist, may care how much you scan and build. They are not written as dollars here. Shape of the bill is subscription plus usage. Solo is not a published tier with a floor.

If a seller offers you "solo lite, hunt only," they are describing LeadsGorilla or a scraper. Those are lighter. Use them if that is the job.

Which agents does a single seat touch, and which sit idle on purpose?

Touch Scout, Radar, Forge, Relay, and Steward every week you are selling. Touch Pulse so the board is not a notes app. Touch Atlas when you want a leave-behind. Touch Echo, Muse, and voice when the finding asks.

Nova can be the only chrome you look at if you like sentences. It still routes to those specialists. Idle agents are not a waste. They are how leftover findings have a home in month two.

You are the approver. Supervised is how a single seat avoids a 1am send. Autonomous dispatch without a second pair of eyes is a choice you make later, action by action, after you can describe what happens if you are wrong.

Watchtower sits idle until you have saved rows. Turning it on against an empty book is theater. Turning it off after you have fifty stale saves is how a solo repeats Monday forever.

How does a one-seat Autonomy Matrix differ from a ten-seat matrix?

The matrix object is the same: per agent, per action, four locks you cannot enable. The difference is who flips it. At one seat, you flip it. At ten, a principal should own Relay and DEPLOY even if juniors run Scout.

There is no "solo safe mode" beyond Supervised. We will not invent a babysitter agent. You are the babysitter.

Kill switch, when you need it, is yours to hit. A single seat still needs one. A sequence that should have stopped, a key that leaked in a screenshot, a contractor you should not have shared a login with: stop, then fix.

Sharing your one seat with a contractor to stay "solo" on paper is how you become a small team without the role talk. Read Small team before you share. Do not share a sender. Do not share DEPLOY.

What does Monday look like when nobody else will run the hunt?

Monday you pick one ICP, not four. A single seat that hunts dentists, roofers, cafes, and clinics in one morning will diagnose none of them. Scout is fast. Radar is not a glance. Forge is a sitting. Be honest about throughput.

Save five, not fifty. LeadScore will fill a page. Your week will not. Pulse should show a board you can finish. Watchtower can hold the rest as timing, not as guilt.

Places key is yours. Optional keys wait. Unknown is fine. A solo who connects seven sources on Monday and sends on Monday is the wasted-week story with extra tabs. Google Places first. A sending domain you control is second if you will mail this week. GBP OAuth, voice, and review networks wait until a finding asks.

ICP exclusions matter more when you are alone. Existing clients, chains, verticals you cannot fulfill. Every junk save is an hour you will not get from a colleague.

What does Wednesday look like when you are the strategist and the builder?

Wednesday you diagnose two. You build one DEMO. You draft one sequence. If that sounds slow, compare it to a week of list, PDF, blank site, and generic mail. The sitting is the product.

Do not batch twenty DEMOs to feel industrial. Sample-first works because the artifact is real and specific. Twenty thin previews is a new kind of spec work.

Atlas the one you will actually walk through. A branded memo for a row you will not call is stationery.

Verify the domain before you fall in love with the draft. The gate does not care that you are one person and "it is only a test."

What does Friday look like when you are also the account manager?

Friday you either have a conversation on your calendar or you do not. If you do, Steward is ready. If you do not, Watchtower and Pulse still have jobs. Filling Friday with more scraping is how solos avoid the send and the follow-up.

Portal setup is yours. Plain language. One business. No costs. No internal notes. You will be tempted to write yourself a reminder on the portal. That reminder is an internal note. Keep it in Steward.

Invoicing, when live, is you. The invoice runs on your own Stripe account, marketer to client. A single seat still should not mix DEV into the invoice. FEE is what you charge.

Time off is a size problem. Autonomous Relay while you are on a plane is how a solo comes home to a burned domain. Pause sequences. The product will not know you are in the air unless you tell it. Watchtower can keep diffs while you are gone. Timing findings wait. A send cannot invent a colleague. If a contractor covers you, read Small team before you share the login. Do not share a sender.

Which compliance lock is least optional when there is no reviewer?

All four locks, plus the domain. Without a reviewer, the gate is the colleague. Unverified mail, cold voice, cold SMS, and gated collect are how single-seat brands die in public.

ADA and privacy drafts need an outside reviewer even more when you are alone. Professional review recommended is not a solo exemption.

Medical and legal verticals need the industry pages before you hunt them by yourself. No EHR. No HIPAA claim. No review blast for a law firm. You will not have a specialist down the hall to catch the sentence.

Yelp and Tripadvisor stay assisted. Do not tell a client you are live there because you are small and "they will not check." They will check after a bad reply.

How should a solo think about DEV, FEE, and modeled dollars without a finance person?

DEV is not rent. FEE is not a promise of DEV. LeadScore is not FEE. Write those on a note if you have to. Pulse forecasts FEE. Atlas refuses bare dollars. Believe the labels.

A single seat underpricing a site because the modeled chair-hour number looked big is how you work for free. The modeled number is their leak, estimated. Your fee is your week.

Health bands exist so you do not put their revenue on a dashboard. Healthy, Watch, or At-risk. You will know their revenue if they tell you. The product will not ask you to display it as a health metric.

We will not give you a solo ARPU to put in a tweet. Invented traction is banned on this site. It should be banned in your head too.

When should a one-person shop stay on lighter tools?

Stay lighter if you only need names, or only need a site, or only need mail volume, or only need rank PDFs. Those tools are better at being small.

Move here when the hop between those tools is the job. One seat feels the hop more than a ten-person shop. That is the size argument, not a moral one.

Apollo still wins LinkedIn titles. Instantly still wins volume. Lovable still wins isolated sites. GoHighLevel still wins a mature CRM you already live in. None of that changes because you are alone.

If you are alone and selling to VPs, you are on the wrong size page and the wrong product page. This loop is local SMBs as customers.

What breaks first when a solo pretends they are an agency?

Senders and portals. One domain for twelve unrelated shops. One portal habit that starts including two businesses because it is faster. That is the agency fear arriving early.

White-label promises. A solo who sells "your own AI platform" in v1 is selling a Not doing. Isolation is real. Resale is not.

Overnight autonomy. A solo who flips every action to look like a bigger firm is borrowing risk they cannot staff.

Vertical soup. A solo who hunts medical, legal, and restaurants in the same week will miss every honest limit. Pick a pack. Industry pages exist so you can.

How does a solo seat become a small team without a migration project?

Add a human to the same tenant when you trust them with a role. Read Small team first. Decide who owns Relay and DEPLOY. Do not hand a contractor the Places key in Slack.

The business uuids stay. Steward stays. Pulse boards stay. You are not exporting a CSV to a new product because you hired.

If the hire is a second brand, that may be a second tenant. Size is not the same as legal entity. Agency isolation rules apply the moment two books exist.

There is no published upgrade fee here. When commercial policy exists, seats and meters will show up on /pricing. Until then, waitlist language stays.

How should a solo use ICP so Monday does not become four metros?

Write one hunt you can fulfill this week. Vertical, metro, a problem, exclusions. Dentists with no booking in one city is an ICP. Quality businesses in the Southwest is a paragraph Scout cannot run.

Tomorrow you can run the same object again. That is the point. A solo who rewrites the prompt every morning is doing theater. Watchtower then has nothing stable to re-scan.

Exclusions save more hours than new sources. Existing clients, chains, verticals you cannot DEMO, the shop that already yelled at you. Put them in the profile. LeadScore will still rank junk if you let junk into the hunt.

When you add a second ICP, finish the first board's diagnostics. Two hunts with twenty saves and zero DEMOs is the wasted week with a better vocabulary.

What does sample-first look like when you are also the person who answers the inbox?

The mail has a problem and a link. You approve it. When they reply, the sequence stops. You are the junior who classifies interested, question, not now, unsubscribe. Suggested reply is still gated. You still click.

A solo who keeps Instantly running a second sequence on the same domain is the collision a small team has, without the second seat. Stop-on-reply only works if all the mail is in the inbox that knows about it.

Book links go to your calendar. If you are out, pause the sequence. Autonomous Relay while you cannot answer is how a good DEMO dies next to a three-day silence.

Do not stack four follow-ups that restate the DEMO. One specific sentence, then a human reply. Volume is Instantly's win. The sample is ours.

How does Steward keep a solo from restarting the client in a notes app?

The uuid continues. Leftover findings are the month-two list. Health is a band. Renewals are dates. The portal is what they see. Your notes stay off that surface even when you are the only one who would read them.

Invoices, when live, are you to them. DEV does not belong on the invoice. FEE does. A solo who pastes a modeled chair-hour number into Stripe is lying with extra steps.

Upsells are leftovers, not a brainstorm on Sunday. If Radar named collect and you only shipped the book button, that is the conversation. If you never diagnosed, Steward cannot invent the leftover.

When you hire, the record is already there. Small team is a seat change, not a migration. That is the size argument for starting on the loop even when you are alone.

How should a solo connect keys without turning Monday into a settings week?

Google Places first. Search cannot run without it. The key is yours, encrypted, masked in the browser. Facebook adds page signals, Yelp discovery needs a paid Fusion plan, and Yellow Pages has no supported discovery API. A solo who spends Monday on seven integrations and sends Tuesday from Gmail has the wasted week again.

A verified sending domain is the second connection if you will mail this week. Unverified is a block. A test on a domain you can burn is allowed. A test on a client-looking domain you do not own is not.

GBP OAuth, voice providers, and review networks wait until a finding asks. Designed is not live. Do not sell a write-back you have not exercised.

Job boards, permits, and license feeds stay off until you can fulfill their sentences. A green check from a missing feed is a lie you will tell yourself because you are alone and want the dashboard to look busy.

How should a solo use Nova so the agent screen does not become a stall?

Type a job the specialist already has. Find, diagnose, build, draft. Nova routes and comes back last. A paragraph about growing your business will get you generic work and a wasted sitting. The homepage mock exists because a vertical sentence is the unit.

If you hate clicking modules, Nova is the door. If you hide in the chat because sending scares you, you are back in the notes-app week. The DEMO link still has to leave through Relay and the gate.

Slash-delegate when you already know the specialist. Do not run five contradictory prompts on one uuid in an hour and call it iteration. You have no colleague to undo the mess.

How should a solo treat unused agents without deleting the loop?

Idle Muse, Echo, or voice is not waste. They are how leftovers have a home. Deleting them from your head so the week looks simpler is how you become a list tool again. You can ignore a module. The vendor should not remove it to make one seat look cheap.

Watchtower stays off until you have saves. Then it stays on. A solo who hunts a fresh metro every Monday because the saved set felt stale is paying for the wasted week with extra Places quota.

Idle Relay is different. If the domain is unverified, you are not in Win yet. Finish Places, diagnose, DEMO, then verify. The loop has an order. Skipping to Nova chat to feel busy is a stall with a nicer screen. One sitting in that order beats four tabs that never share a uuid. That order is the whole size argument.

How does a one-person shop join the waitlist as Solo, not as a fake team?

Say you are one human, which verticals, which metros. Do not invent two colleagues to look like an account worth a batch. We would rather give a seat to someone who will actually run the loop.

Use the first-client guide while you wait. It assumes no staff.

When access opens, connect Places, one ICP, small save set, two diagnostics, one DEMO, verified domain, Supervised send. That is the size-appropriate week.

If you came here from Solo marketers, you already know the fear. This page's last job is to say the modules do not shrink because you are alone. Get started when you want the next batch.

What happens when a solo is sick and Relay is still Supervised?

When a solo is sick and Relay is still Supervised, drafts sit in the queue and nothing leaves until you click. That is the point of one seat. There is no junior to clear Approvals. Pause sequences before you disappear. The product will not know you have a fever unless you tell it.

Autonomous Relay while you cannot answer is how a good DEMO dies next to a three-day silence. Stop-on-reply only works if you are the human who reads the inbox. Book links go to your calendar. If you are out, the meeting still belongs to you.

Watchtower can keep diffs on the saved set. Timing findings do not require you to hunt a fresh metro from bed. A rating drop or a permit can wait a day. A send cannot invent a colleague.

If a contractor covers you, you are no longer solo on paper. Read Small team before you share a login. Do not share a sender. Do not share DEPLOY. Sharing your one seat to stay solo is how you become a small team without the role talk.

How does a solo keep DEV off the invoice without a bookkeeper?

A solo keeps DEV off the invoice without a bookkeeper by treating DEV as modeled recovery for the SMB and FEE as what you typed into Stripe. Write those on a note if you have to. Pulse forecasts FEE. Atlas refuses bare dollars. A modeled chair-hour number pasted into an invoice is a lie with extra steps.

LeadScore is not FEE. Opportunity score is not FEE. Health is a band, not their revenue. You will know their revenue if they tell you. The product will not ask you to display it as a health metric.

payment_setup.requested is how a Forge offer becomes a draft bill. You confirm. Steward does not invent a package. We will not give you a solo ARPU to put in a tweet. Invented traction is banned on this site. It should be banned in your head too.

A single seat underpricing a site because the modeled number looked big is how you work for free. The modeled number is their leak, estimated. Your fee is your week. Invoices, when live, are you to them. The invoice runs on your own Stripe account, marketer to client.

What should a solo refuse to automate in month one?

A solo should refuse to automate Relay.send, Forge.deploy, and Muse.publish in month one. Raise Scout.search if you want. Leave amber cells amber until you have approved a week of artifacts and liked them. The grid is not a score. Empty green is not maturity.

Refuse overnight prospecting as a live run. Dry-run the card. Read the tier ribbon. Governance is live. The runner is the open half. A solo who flips every action to look like a bigger firm is borrowing risk they cannot staff.

Refuse cold channels. The four locks do not soften because you are alone. Unverified mail, cold voice, cold SMS, and gated collect are how single-seat brands die in public. ADA and privacy drafts need an outside reviewer even more when you have no specialist down the hall.

Refuse white-label promises. A solo who sells your own AI platform in v1 is selling a Not doing. Isolation is real. Resale is not. Refuse vertical soup. Hunt one pack. Industry pages exist so you can.

How does Watchtower replace Monday scraping for one seat?

Watchtower replaces Monday scraping for one seat by re-scanning the rows you already saved and handing you diffs instead of a new dump. A rating drop, a permit, a hours change. Freshness has a clock. A stale save is a wasted send you will not get back from a colleague.

Turning Watchtower on against an empty book is theater. Turning it off after you have fifty stale saves is how a solo repeats Monday forever. ICP exclusions matter more when you are alone. Existing clients, chains, verticals you cannot fulfill. Every junk save is an hour.

Save five, not fifty. LeadScore will fill a page. Your week will not. Pulse should show a board you can finish. Watchtower can hold the rest as timing, not as guilt. Places key is yours. Optional keys wait. Unknown is fine.

A solo who hunts a fresh metro every Monday because the saved set felt stale is paying for the wasted week with extra Places quota. Tomorrow's hunt should be the same ICP object. A prompt you rewrite every morning is theater Watchtower cannot attach to.

When does one seat become two books by accident?

One seat becomes two books by accident when you put two legal brands, two senders you should have split, or two portals that start including two businesses because it is faster. That is the agency fear arriving early. Isolation is storage and discipline even when the headcount is one.

One domain for twelve unrelated shops is convenient and fragile. When a complaint arrives, you stop. Tighter senders cost setup. They save the book. White-label promises to a client who wants their own AI platform are still Not doing.

If the hire is a second brand, that may be a second tenant. Size is not the same as legal entity. Agency isolation rules apply the moment two books exist. The business uuids stay. You are not exporting a CSV to a new product because you hired.

There is no published upgrade fee here. When commercial policy exists, seats and meters will show up on /pricing. Until then, waitlist language stays. Read Small team before you share. Read Agencies when the leak is the fear. Stay here for the seat count.