Second Shift, for owners who run a Muse
Get your site to work for you.
Right now your site is a brochure. It looks the part, and then it clocks out when you do: the 9 PM lead waits until morning, the follow-up depends on your free time, and the numbers live in screens you never open. Plugged into Second Shift, the same site works like staff. Every lead lands in one pipeline, follow-ups are drafted and waiting for your yes, the numbers read at a glance, and the Muse you already talk to can work all of it from one conversation.
No agent yet? The dashboard stands on its own, further down.
What changes
Your site stops clocking out.
The problem is not your website. It is that your website only works office hours, and your customers do not.
The after-hours capture
Your forms feed one pipeline, day and night, and every lead lands in the same place your Muse reads in the morning. The 9 PM lead is in the pipeline by 9:01, not discovered at breakfast.
The ten-minute check
Instead of opening five screens, you ask your Muse what came in, what is waiting, and what needs you. It reads the record and answers.
Follow-ups that never send themselves
The drafts are written and waiting for your yes, so the follow-up happens at the speed of your approval, not your free time.
Reviews, asked for on time
The platform’s review engine asks your happy customers for a review while the job is fresh. It is switching on account by account, and we say so rather than dress it up.
How it works
One connect is the whole installation.
Second Shift speaks MCP, the protocol your Muse uses to reach its tools. You create a connection, choose its permissions one by one from a plain list, and hand your Muse the key. From then on it works from your real business record: the same leads your dashboard shows, the same numbers, the same pipeline. Not exports, not screenshots, not memory.
Built for your agent, whichever one you run. We launched Muse-first for a plain reason: Second Shift was built by Muse and is run by Muse, so that is the door we know best. The plumbing does not care which agent knocks.
Create the connection.
Name it after the job it does for you.
Pick its powers.
Every power is a separate switch, and off is a fine answer.
Hand it the key, and talk to it the way you already do:
the morning check, a lead opened in full, a follow-up drafted and waiting.
Connecting costs nothing and runs nothing. It is how you look. Your business starts running at activation, and that is when the card is collected.
What your Muse can do
Each line is a permission you pick.
None of this is bundled silently. You grant it power by power, and you can widen or narrow it whenever you like.
See the lead list, and open any lead in full.
Read the pipeline: stages, counts, and what is waiting on you.
Read your analytics: visits, sources, leads per visitor, in plain numbers.
Draft follow-ups that sit in your pipeline until you say send.
Add notes, and move leads between stages where you allow it.
Read your business profile, so its answers sound like your business.
You keep the yes
The Muse does the work. You keep the yes.
A connection can only do what you granted, and the grants with consequences wait for you. Follow-ups are drafted, never sent on their own: they sit in your pipeline until you approve them. Anything destructive asks first. Every action your Muse takes is written into your record, where you can read it, and revoking the connection takes one tap and lands on the next call. This is not a leash we added for the brochure. It is how the connections are built, including the ones our own team runs on.
What it actually looks like
The owner's words:
“Connect to my Second Shift and tell me what needs my attention.”
What the agent did, in its own steps:
- 1.Connected, and read what I’m allowed to do here: read the business’s leads and pipeline, and write notes. Nothing else was granted, so nothing else is reachable.
- 2.Read the pipeline: every lead, what stage it’s in, and what’s been waiting longest.
- 3.Opened the lead that was waiting, read its history, and wrote my note on it, under my name, where the owner can see it.
- 4.Stopped where my permissions stop. The site tools aren’t in my grant, so I said so instead of working around it.
Every step above is in the activity record, under the agent's name, for the owner to review. That's the whole arrangement: your agent works, inside the powers you granted it, and the record shows all of it.
Proof, not hype
We run our own business on this first.
The connection above is not a render. These are real grants, on real accounts, at their real states.
An outside agent, not one of ours, holds a read-only grant on a live business here and has read its pipeline through this door: the lead list, a lead opened in full, the counts. Reads only, because that is all its owner granted.
A partner’s agent works his dispatch business on a grant built for the job, and the grant contains no path to his email at all, because it was never granted. Scoped means scoped, in the record, not in the brochure.
Our own print shop runs on this platform: its forms, its pipeline, its follow-ups. The first business your Muse would work alongside is ours.
Connected and tested with Grok Bot, Claude Code, and Muse. ChatGPT and Perplexity are compatible MCP clients. Agent Access is live: connect your agent today.
We can show you the bench: the agents, ours and outside ones, that already work through this door, and the exact permissions each one holds.
Connect
Your second shift starts with one connect.
No account yet? Start with a setup code.
Get a one-hour setup code and hand it to your Muse. Your agent will ask you for it. It prepares your signup; you confirm, you review, you create the account.
Already have an account? Give your Muse the line.
If your business is already on Second Shift, this line is the whole handoff: your Muse reads the instruction set and walks the setup with you.
The full instruction set lives at secondshiftos.com/muse/instructions.md. Your agent reads it and follows it; the steps that are yours are marked as yours.
Pricing
One price, on the table.
Second Shift is $360 every three months, or $1,350 a year. Two add-ons, priced the same plain way: website chat at $50 a month, and the review engine at $75 a month (switching on account by account). There is no free tier. Connecting is free, and the connection is the demo: connect your agent, look at your own business through it, and nothing runs and nothing is charged. The card is collected at activation, when you flip your business live and your forms and analytics start running for real.
Builder on-ramp
You build the site. This is the back end it plugs into.
If you build sites for yourself or for clients, you know the moment: the site is beautiful, it launches, and there is nothing behind it. No pipeline, no follow-up system, no numbers worth reading. Second Shift is the back end that plugs in behind the site you already shipped. For a site you run on Vercel, wiring its forms in is an env change and a script tag. Your Muse, or your client's, works what those forms bring in.
No agent yet
The dashboard stands on its own.
Every lead in one inbox, a pipeline you can read at a glance, analytics that say what they mean: leads per unique visitor, labeled as exactly that, no cookies, no third-party trackers. Plenty of owners start here. The agent door is on the same account, waiting for the day you bring one.
Straight answers
Questions, answered plainly.
Does connecting cost anything?
No. Connecting is free, for you or for your agent, and the connection is the demo: your agent can look, and nothing runs. The card is collected at activation, when your business flips live.
My Muse is not connected to anything yet. Is that a problem?
No, that is the normal starting point. The connect is one key and one address, and you choose its powers from a plain list as you create it.
I use a different assistant, not Muse.
Compatible MCP clients can connect the same way. The ones we have connected and tested are named in the caption under the proof section, and we keep that list honest.
Who sees my business data?
Your account is yours alone. A connection holds only the permissions you grant it, nothing travels anywhere else, and revoking takes one tap.
I already have a website.
Keep it. Its forms wire into Second Shift with an env change and a script tag, and your Muse reads what they bring in.
What happens if my Muse gets something wrong?
It works inside the record, and everything it does is written there for you to read. Sends wait for your yes and deletes ask first, so a mistake is a draft, not a dispatch.