Copilotly

For teams

The departments you do not have.

Companies under about fifty people have the same legal, HR, finance and compliance questions as companies of five hundred - and none of the staff to answer them. The usual outcome is not that the questions get answered badly. It is that they get postponed until they become expensive.

What actually happens without one

The employee handbook has no grievance procedure until there is a grievance. The contractor agreement gets signed unread. Quarterly estimates get missed and the penalty arrives in April. A long-term contractor works set hours on company equipment for two years and nobody asks whether that is still a contractor relationship.

Nobody made a bad decision. There was simply no one whose job it was to look, and every one of those questions sat below the threshold that justifies a $400 phone call - right up until it did not.

That threshold is the actual problem. It is not that small companies are careless; it is that professional advice is priced per hour and most of these questions are ten-minute questions. So they accumulate.

What the gap costs, concretely

The compounding is easier to see with numbers attached, so here are the four that show up most often at this size.

Worker misclassification
Back taxes, unpaid overtime, penalties and interest, and both federal and state agencies pursue it independently. The tests turn on control rather than on what the contract says it is, which is exactly the part founders get wrong. One of the most expensive mistakes available at this size.
An undocumented performance problem
Two quarters of unrecorded concern is not a performance case, it is a feeling. Acting on it creates exposure rather than resolving anything, and employment claims overwhelmingly originate here.
The clause nobody read
Indemnification, limitation of liability, auto-renewal and a dispute-resolution clause committing you to arbitration in another state. Each is three paragraphs and each decides what happens on the worst day of the relationship.
Cash confused with profit
A profitable company that cannot make payroll because customers pay in sixty days and suppliers want thirty. Growth consumes cash, and the faster it grows the more it consumes - which is why fast-growing companies fail.

None of these needed a department. Each needed somebody to ask one question at the right moment, and the reason nobody did is that asking cost several hundred dollars before anyone knew whether there was anything to ask about.

Where teams actually use it

Six of the 20 domains do most of the work inside a company. Every seat gets all 131 regardless - problems do not stay in one lane, and a legal question usually has a tax consequence attached.

What the first week looks like

Internal tools fail on adoption rather than on capability. The teams where this sticks do roughly the same four things.

  1. Start with a real question, not an announcement. Someone asks in Slack what the notice period is, or whether a clause is normal. The answer is a link to the conversation. That is a demonstration; an email about a new tool is not.
  2. Give it to the people who get asked things. Whoever currently fields the HR, finance and contract questions is the highest-leverage first seat, because they are the bottleneck the whole company is queued behind.
  3. Write down the things that only live in one head. The invoicing routine, the deployment step, the onboarding checklist. Half an hour each, and it exposes the steps that exist for reasons nobody remembers.
  4. Set the boundary out loud. This prepares questions for professionals; it does not replace them. A team that is clear on that uses it well. A team that is not will eventually use it for something it should not.

What Enterprise adds

Pro is the right answer for most teams under about twenty people. Enterprise starts to matter when procurement, identity management or data handling become someone’s responsibility.

  • Unlimited seats, with an admin dashboard and usage analytics - which is also how you find out whether anyone is actually using it.
  • Custom copilots grounded in your own handbook, contract templates, runbooks and documentation, so answers cite your policy rather than the general case.
  • SSO and SAML, so access follows your identity provider and offboarding is one action rather than a checklist.
  • API access for internal tooling, if you want copilot answers inside something you already run.
  • A dedicated account manager, a custom SLA, and SOC 2 documentation for the security review you will be asked to pass.

Pro is $29/month per seat and covers everything else. See the full pricing breakdown, or talk to sales for a real quote rather than a form.

Security and data handling

The short version: encrypted in transit and at rest, never used to train models, never shared, deletable at any point. Uploaded documents are scoped to the workspace that uploaded them.

Enterprise adds workspace-level isolation, admin control over retention, export, and SSO-driven access. SOC 2 documentation is available for security review.

If you are handling regulated data - PHI, card data, regulated client records - talk to us before you buy. We would rather have a specific conversation than tell you it is fine for a category we have not discussed. The full detail is in the privacy policy.

What it will not do

Stated plainly, because a company that buys this to replace counsel will find out at the worst possible moment.

  • It is not a law firm, an accounting practice, or a certified HR function, and it does not create a privileged relationship.
  • It cannot file anything, sign anything, or represent your company before any agency.
  • Harassment, discrimination, termination and wage-hour classification go to an employment attorney. Every time, and it will keep saying so.
  • Anything you will actually sign gets reviewed by a lawyer. Use this to arrive knowing which three clauses you want to discuss.

That boundary is the point rather than a disclaimer bolted on. Tools in this category have been fined for implying otherwise, and a team that understands where the line is gets considerably more out of the tool than one that does not.

Team and Enterprise questions

What does Enterprise include over Pro?

Everything in Pro, plus unlimited team members, custom copilots trained on your own data, SSO and SAML, an admin dashboard with usage analytics, API access, a dedicated account manager, a custom SLA and SOC 2 documentation.

Pro is the right answer for most teams under about twenty people. Enterprise starts to matter when procurement, SSO or data residency become someone's job.

Can we train copilots on our own documents?

Yes, on Enterprise. Custom copilots can be grounded in your handbook, your contract templates, your runbooks and your product documentation - so answers reflect how your company actually does things rather than the general case.

That is usually the difference between a tool people try and a tool people keep open. Generic advice is easy to ignore; advice that cites your own policy is not.

How is team data isolated?

Conversations are encrypted in transit and at rest and are never used to train models. Enterprise adds workspace-level isolation, admin control over retention, and export.

Uploaded documents are scoped to the workspace that uploaded them. One team's contract templates are not reachable from another team's copilot.

Does this replace our lawyer or accountant?

No, and a company that buys it for that reason will be disappointed at the worst possible moment.

What it replaces is the hours your team currently spends either guessing or waiting. For anything consequential it prepares the question rather than answering it - which usually makes the professional engagement shorter and therefore cheaper.

How does billing work for a team?

Pro is $29/month per seat, or $290/year per seat annually. Seats can be added and removed as the team changes.

Enterprise is custom and depends on seats, data requirements and support level. Contact sales and you get a real quote rather than a form.

How long does rollout take?

For Pro, minutes - people sign in and start. There is no implementation project, because there is nothing to implement.

Enterprise with SSO and custom copilots is measured in days rather than months: identity provider configuration, then loading whichever documents you want copilots grounded in.

What if people do not use it?

That is the real risk with any internal tool, and the honest answer is that adoption follows a specific trigger rather than an announcement.

The teams where it sticks introduce it at the moment of a real question - someone asks in Slack what the notice period is, and the answer is a link. The teams where it does not are the ones that sent an email about a new tool. Usage analytics on Enterprise will tell you which you are.

Can we use it for regulated or client data?

Talk to us first. SOC 2 documentation is available on Enterprise, and workspace isolation and retention controls cover a lot of requirements.

What we will not do is tell you it is fine for a category we have not discussed with you. If you are handling PHI, card data or regulated client records, that is a conversation with specifics rather than a checkbox.

Try it on your own case

Get help with this from the Business & Strategy Copilot

Describe your situation and get specific, actionable guidance - not the generic hedging a general-purpose chatbot gives you on business & strategy questions.

Free plan, no card. Pro from $4.99/week for every copilot across all 20 domains - about what one hour with any single professional costs per year.