One system.
The whole job, end to end.
Piquup isn't a phone bot — it's a manager for the whole life of a business. The chapters below run in the order a business lives them: born, banked, operating, growing. Start at chapter one, or start wherever you already are.
How starting a company will work.
Where the arc begins. Piquup starts at the day a business is born — and hands you an operating company, not a folder.
You answer plain questions.
The name, the state, who owns what — asked in plain language, once. No forms decoded at midnight, no guessing which box means what.
The formation packet is prepared — LLC first.
Formation filings, the EIN route, and a compliance calendar that watches your filing dates so you never learn about a deadline from a penalty notice.
The company is born operating.
Not a stack of documents — a business that exists and works: a number that answers, a business email, a workspace ready for the team, from day one.
The company gets its accounts.
The first step connects the account the business already has; full banking and the back office follow on the same record. Sparse on purpose: the chip means it.
It connects to the bank account you already have.
Read-only — Piquup sees deposits and payments and matches them to the customers and bookings that earned them, so the revenue numbers in the dashboard are real, not estimates.
A business account beside the bookings that pay into it.
Banking planned where the revenue already lives — so money in has context the day it arrives, matched to the jobs that earned it.
Payroll & HR, taxes, bookkeeping — one company record.
The back office carried on the same record the manager already keeps: the books read from the bookings, payroll reads from the team, taxes read from both.
Nobody has to start at chapter one. Already incorporated? Piquup picks up at compliance and runs everything forward. Just want the phones handled? Start at the calls and add the rest when you're ready. Every piece you turn on writes to the same record — and everything works from the dashboard, or from Claude, Codex, or ChatGPT once the agent connection ships.
From first ring to logged record.
The operating core — and the part running live right now, on real phone lines: your number, your voice, your real calendar.
It rings on your number.
Your customer dials the same number they always have. Nothing new to advertise, nothing for them to install — the manager sits behind the line you already own.
Answered before the second ring.
Picked up in the voice you chose, under your business name, with your greeting — 2 AM, Sunday, lunch rush. No hold music, no voicemail, ever.
Returning customers are recognized.
The inbound number is checked against your customer history before the first hello. If they've called before, their record is already open — last visit, preferences, notes — so regulars get greeted like regulars.
The conversation.
Intake runs per service — it asks the questions you'd ask, and books the length the job actually takes. It reads your calendar live before offering a time, applies your booking rules, and hears urgency for what it is, so an emergency gets treated like one.
Confirm and send.
The event is written to your calendar, the confirmation text goes to the customer, and if the call clears the bar you set, a heads-up lands on your phone — all before the caller has finished saying goodbye.
Logged where it lives.
Full transcript, a summary, and every captured field are saved to the dashboard, on the customer's record. You review what you want; the rest just runs.
When it shouldn't guess, it asks.
Anyone can take a message. Here's what happens when a caller asks something only your team would know.
A caller asks something the AI shouldn't guess.
Warranty terms, a custom job, a judgment call. The manager knows the edge of its own knowledge — it won't put your name on an improvised answer.
The question is texted to the teammate who'd know.
One clean question, straight to the right person's phone — no app to open, no ticket queue. Meanwhile the customer's thread stays warm; nobody hears "someone will call you back."
One line back is all it needs.
"If we installed it, it's covered." That's the whole job for your teammate — one text, sent whenever there's a gap between ladders.
The customer gets a polished answer — from the business.
The one-liner comes back as a finished, professional reply sent from your number, not somebody's personal cell. Minutes end to end.
The whole exchange is logged.
Question, answer, and outcome land on the customer's record — so the next person who opens it sees exactly what was promised.
The manager runs the inside, too.
Not just customer conversations — the handoffs between your own people, employee to employee, department to department.
An invite link is the whole onboarding.
Send a link, teammate taps it, they're in. No software rollout, no training day, no IT project.
Each teammate opens their own seat.
Their questions, their calls, their view — everyone sees their own queue, not the whole firehose. The manager decides who needs what and carries it to that seat, so nothing depends on someone remembering to forward a message.
Departments get their own lines.
Estimates, service, billing — each line with its own voice and its own instructions. A caller who reaches the estimates line meets the estimates department, and a handoff between departments is the manager's job, not a transferred call that dies on hold.
Everything still writes to the same records.
Whichever seat or line a conversation touches, it lands on the one customer record — so an internal handoff carries the full history with it, and nobody starts from zero.
Nobody types up notes after.
Every conversation the manager has becomes memory the whole business keeps.
Every conversation writes itself down.
Each call, text, and email lands on one customer record as it happens — transcript, summary, captured fields. The same person is the same record whether they call, text, or email.
History, preferences, notes accumulate.
What they booked, what they asked, how they like to be reached, what to remember next time. The profile deepens with every contact — no one maintains it, it maintains itself.
Your whole team works from it.
Every seat reads the same record, so no customer repeats themselves — and what one teammate promised, the next one can see before picking up the thread.
Yours, and exportable any time.
Your customers' conversations stay your customers' conversations — nothing trains shared models, and every transcript and record exports whenever you ask.
The money follows the booking.
The manager that books the job should be the one that collects for it. Here's how that's coming together.
Checkout already has a surface in the product.
The screens exist inside the dashboard today — the place where a booking becomes a bill, sitting right next to the record that booked it.
The payment rails are being built.
Stripe-powered payments are in development — so the same records that booked the job can bill for it, without a second system to reconcile.
Deposits on bookings follow.
A job booked with money down is a job that shows up. Deposits ride the same rails, attached to the appointment itself.
Nothing moves money without you.
Anything that charges, refunds, or pays out waits for your approval in the dashboard. The manager prepares it; you say go.
Analytics you never have to enter.
The capture powering this is live today; the analytics surface on top of it is in development — the chip means it.
Every conversation is already structured data.
Because the manager handles the calls, texts, and emails itself, each one arrives pre-structured — service, source, outcome, urgency. This part runs live today, on every conversation, with no extra bookkeeping from you.
The dashboard assembles the picture.
Busiest hours, booking rates, revenue per service — read straight out of the records the manager already keeps, instead of a spreadsheet night. This is the surface being built now.
It tells you who to call back first.
Prioritization reads the same records — hot leads surface to the top, follow-ups get ranked — so the first hour of your day is aimed at the highest-value work, not the most recent voicemail.
The manager, wherever you work.
If you live in an AI agent, the manager comes to you.
Connect from Claude Code, Codex, or ChatGPT.
One connection from the agent you already work in — headed for the plugin stores, and chipped honestly until it ships.
It signs you in with your Piquup account.
The agent and the dashboard become two windows onto the same business — same customers, same calendar, same memory.
Agent-runnable services run in the agent.
Briefings, records, loop-closing — run right where you're typing. Anything that moves money still waits in the dashboard for your approval.
Watch it run on your business.
Book 15 minutes — your services, your calendar, your questions, answered chapter by chapter.