About AppSuiteHQ
A note from the team · September 2026
Every small business has a chief of staff. It’s the owner.
They read the CRM, chase the invoices, check the budgets and remember what was agreed, usually after the client work is done. We build AppSuiteHQ so that job is done before they sit down in the morning.
01 · The argument
The problem isn’t a missing tool.
Take a design studio of eight people. It sells hours. To know whether this week is going well, the owner opens the CRM, the proposal tool, the contracts folder, the timesheets, the accounting package and the spreadsheet that ties them together. Each of those tools is good at its job. None of them can tell her that the client who owes the most also has a proposal going quiet and a project running over budget.
Another tool doesn't fix that. Every new one adds a place to look and an export to reconcile. The information is already there. What's missing is something that reads all of it, every morning, and says what matters.
An illustration. On the left, six open browser tabs late on a Sunday evening: the CRM, a proposal, a contract, timesheets, overdue invoices and a cash spreadsheet. On the right, Monday's 7:00 briefing for Northwind Studio: Harbor & Pine owes $12,400 and has paid late twice this year, with three things to do today.
The owner shouldn’t be the integration.
That is what we mean by an operating system for a business: one record for clients, projects, time and money; rules that notice what needs attention; drafts prepared from the record; and a person who decides what leaves. The thirteen tools are still there. They're how the work gets into the record, not thirteen more things to check.
02 · How we got here
From thirteen tools to one operating system.
AppSuiteHQ started as a suite. It became an operating system once we saw where the real work was: in the gaps between the tools.
2025
Thirteen tools, one database
We built the suite we wanted as small-business owners: CRM, proposals, contracts, projects, time, accounting, expenses and six more, sharing one database.
May 2026
One loop, done properly
The tools worked; the gaps between them didn't. We picked one loop for agencies and professional firms, proposal to cash, and built a queue of the proposals, contracts and invoices that needed a person, with thirty minutes to flag a mistake.
September 2026
One record
Every client became one account across the tools, and every change became an event. Signals computed by rules you can read, the Command Center and a morning briefing replaced the grid of statistics on the home screen.
Now
Lead to cash to profit
Margins per project and client, a 30-day cash forecast with its likely range, capacity for next week, and follow-ups prepared from the record, waiting in one approval inbox.
Next
Policies, teams and specialist agents
Routine actions that run within limits you set, team roles and permissions, then specialist agents. Money and permissions stay with people.
03 · What we believe
Five beliefs, and what each one rules out.
Drafts, not decisions.
The AI prepares and a person decides. Reminders, follow-ups and proposals are written for you and wait in one inbox until someone approves them.
In practice
Nothing is sent on its own.
Figures as recorded, with their sources.
Every number says where it came from: the invoice, the payment, the hours. We don't connect to bank accounts, so we say “as recorded”, and a forecast always shows its likely range.
In practice
A draft can't mention a figure the record doesn't have.
A number without a source is an opinion.
An example payment reminder to Harbor & Pine in which every fact is traced to where it came from: $12,400.00 and the due date from invoice INV-00041, Dana Reyes from the contact record, and the accounts-inbox instruction from memory.
Autonomy is earned, by risk tier.
Reading runs on its own. Preparing waits for your review. Changing records, and anything that leaves the business, waits for your approval each time.
In practice
Moving money, deleting records and changing permissions: people only, never the AI.
One record, not integrations.
Copying data between separate tools leaves gaps exactly where problems hide. The deal, proposal, contract, project, hours and invoice live in one record, so each one carries the one before it.
In practice
Nothing typed twice.
Calm software.
Three things to do today, not three hundred notifications. The briefing arrives at the hour you choose, signals are ranked by what they're worth, and the rest stays quiet until it matters.
In practice
If it isn't worth your morning, it waits.
04 · How we build it
Plain choices, written down.
The parts of AppSuiteHQ that touch your data and your decisions, and what we chose for each.
An example audit log for one payment reminder at Northwind Studio: prepared by the assistant at 7:02 as a tier 1 draft, approved and sent by Maya at 9:14 as a tier 3 action, with 30 minutes, until 9:44, to mark it sent by mistake.
- The model
Claude, through Anthropic's commercial API
Answers, briefings and drafts are written by Anthropic's Claude. Under the commercial terms, your data isn't used to train models.
- The numbers
Computed first, written second
Metrics, signals and forecasts are calculated from your records by code. The model describes them; it doesn't make them up.
- The actions
Registered, tiered and logged
The assistant can only use actions we've registered, each with a risk tier, and never touches the database directly. Who prepared an action, who approved it and what it changed is kept in the audit log.
- The data
Scoped to your organisation
The operating system's records carry your organisation's ID and are protected by row-level security in the database, so one workspace can't read another's.
05 · Who it's for
Small businesses that need to run smarter. Usually between one and fifty people.
Agencies
Retainers and campaigns, and clients who pay on their own schedule.
Studios
Fixed-fee projects where the budget burns before anyone looks.
Consultancies
Proposals, statements of work, and who's booked next week.
Service businesses
Subscriptions, retainers and one-off jobs, and the invoices that follow each of them.
Growing businesses
Products, services or both: more happening than one person can keep in their head.
Not the right fit yet
If you need stock control and a point of sale, live bank feeds or payroll, AppSuiteHQ isn't built for that today. We'd rather say so now.
Run the business, not the tools.
Start with your clients and open invoices. The first briefing can use them the next morning.
No card needed · 7 days of the operating system