Why Roots HQ
We want your business—and we intend to earn it.
Most software companies want your business to fit their product. Roots HQ starts with a different question: what does your business actually need?
We built the platform to run real day-to-day operations, but we are not interested in declaring it finished and ignoring the people who use it. We want your feedback, your feature requests, and your honest account of what slows you down.
What choosing Roots HQ means
A working relationship, not a closed box.
We want to understand your business
We do not assume every company sells, fulfills, markets, or reports in exactly the same way. Before we talk about features, we want to learn how you actually operate:
- How the business sells
- Where orders originate
- How products are managed
- How fulfillment works
- What customers expect
- Which reports matter
- Which processes waste time
- Which existing tools create friction
We want your feature requests
Feature requests are not an inconvenience. They are one of the ways the platform gets better.
We do not promise that every request will be built exactly as submitted. We do promise that useful requests will be heard, evaluated, discussed honestly, and prioritized against the needs of the platform and its customers.
That distinction matters — and we would rather be straight about it than make a promise we cannot keep.
We want to respond
Responsiveness is not a promise of instant magic. It is a way of working:
- Clear answers, not deflection
- Honest timelines
- Useful status updates
- Direct acknowledgement of problems
- No pretending a limitation does not exist
- No endless ticket loop with nobody accountable
We want to grow with you
Roots HQ is meant to become more valuable as the business changes — not to be replaced every time you add a channel, a location, or a way of selling. As you grow:
…the platform should absorb it. You should not need to replace the whole operating system every time the business moves.
One team accountable for the platform
Roots HQ reduces the number of disconnected systems required to operate the business, and keeps one team accountable for how they work together:
Roots HQ does not claim to replace every specialized accounting, tax, legal, payroll, or enterprise system. Where one is genuinely needed, it connects.
Plainly
We want the work.
We want to learn how your business operates.
We want to hear what the software is missing.
We want to build features that solve real problems.
We want to tell you the truth when something is difficult.
We want to respond when you need help.
And we want to keep earning your business after the contract is signed.
Customer-driven development
How a request actually moves.
Not every request is custom code. The first job is to figure out what the need really is — then to be honest about it.
- 01
Tell us what is slowing you down
A specific workflow, a report you cannot get, a step your staff repeats by hand.
- 02
We investigate the actual workflow
We look at how the work really happens today — not how software assumes it happens.
- 03
We identify what the need actually is
Configuration, training, an integration, a tenant-specific customization, a bug, or a genuine platform feature request. These are not the same thing, and we do not bill them as if they were.
- 04
We explain the options honestly
Including cost, effort, and whether it fits the platform. Sometimes the honest answer is “that already exists — here is how.”
- 05
Approved improvements enter a visible process
You can see where the work stands rather than guessing.
- 06
Completed work is tested, documented, versioned, and released
And the person who asked for it hears that it shipped.
We name the request honestly
Treating everything as “custom development” is how customers get overcharged. We distinguish:
- Bug
- Something is broken and should be fixed — not a paid feature.
- Configuration
- The capability exists; it needs to be set up for how you work.
- Training
- The capability exists; the team needs to know where it is.
- Integration
- A connection to a tool you already rely on.
- Tenant customization
- A change specific to your business.
- Platform feature
- A new capability evaluated for everyone on the platform.
Accountability
A platform should not disappear after the sale.
Buying business software should not mean being passed between sales, onboarding, support, and billing teams that do not know one another. Roots HQ is being built around a simpler idea: the people responsible for the platform stay accountable for how it performs.
The common failure in this industry is not that one vendor is careless — it is that accountability gets fragmented across too many vendors until no one owns the outcome. Fewer disconnected systems means fewer seams for responsibility to fall through.
Security
Controls you can actually check, not a badge.
We do not have a compliance certification or a published uptime number, and we are not going to dress the page up as if we did. Here is what is actually built, described plainly — including where it stops.
Getting into the account
- Two-factor authentication (TOTP), available to any user and required at login once they turn it on
- Repeated failed logins lock the account; heavy failed-login volume from one address blocks that address across the whole platform, not only the account it was aimed at
- Sign-in can be restricted to specific countries, or refused everywhere except an allow-list
- Admin access can be restricted to approved IP addresses or ranges, with a safeguard against locking out the last allowed address — and a support path to clear it if that happens anyway
- Platform support staff sign in through a completely separate identity that cannot open a business’s own workspace
What gets recorded
- Sign-in failures, staff changes, password resets, two-factor changes, IP blocks and unlocks, security-setting changes, and discount changes are written to an audit trail
- An entry for a settings change records which setting changed — never the value, so the log itself is never a place a secret can leak
- Resetting or changing a password immediately signs that account out of every active session
Data and payments
- Every workspace’s data is scoped to that workspace at the database level, not left to each screen to get right
- SMTP, payment, and other API credentials are encrypted at rest, not stored as plain text
- A phone taking Tap to Pay payments is issued its own 24-hour access token, revocable individually, and never holds the business’s own Square credential
- Custom domains get a real Let’s Encrypt certificate — automatic HTTPS, not a manual step to remember
Where this stops
- Signing out is all-or-nothing today: there is no per-device or per-session revoke list, only "sign out everywhere" for an account.
- There is no single export or backup of an entire account’s data. Per-module export (CSV/XLSX) exists for contacts, sales, mileage, tax records, and more.
Straight answers
What we will and will not promise.
- Will every feature I request get built?
- No — and we will not pretend otherwise. We promise that a useful request is heard, evaluated, discussed honestly, and prioritized against the needs of the platform and other customers. It will not vanish into a ticket queue with nobody accountable.
- Is Roots HQ a replacement for my accountant or tax software?
- Roots HQ provides operational accounting and profit-and-loss views built around how you actually sell. It reduces the number of disconnected systems you run — it is not a substitute for formal accounting, tax filing, or payroll systems.
- Does Roots HQ replace every other tool I use?
- It reduces the number of disconnected systems required to operate the business. Where a specialized system is genuinely needed, Roots HQ is built to integrate with it rather than pretend it does not exist.
See how Roots HQ fits your business.
A guided walkthrough of the platform, mapped to how you sell.