Question 1

How long until we are actually live?

Accepted Answer

Weeks, not quarters. A typical cloud deployment runs four weeks: week one we map your data and agree the setup, week two we migrate and you check it against your own records, week three runs both systems in parallel, week four you switch. Larger or managed deployments take longer, and we will tell you that before you sign rather than after.

Question 2

Who does the work - us or you?

Accepted Answer

Us. Migration, configuration and the initial setup are done by our team, not sold as a professional services line item. What we need from you is a few hours of the person who knows how your business actually works, which is unavoidable in any system.

Question 3

Do we have to move everything at once?

Accepted Answer

No, and most teams should not. The usual order is Sales and Planning first, then Delivery and Finance once people trust it. The thread is worth more the more of it you have, but a partial move is a real option rather than a fudge.

Question 4

What if our team refuses to use it?

Accepted Answer

That is the actual risk with any system, and it is usually a sign that the tool asks for more than it gives back. The honest test: after week two, is anyone re-typing data into a second place? If yes, something is wrong with the setup and we will fix it.

Question 5

Can we trial it properly before committing?

Accepted Answer

Every plan opens all modules for the first 14 days, and the Launch plan is free indefinitely for one user. For a real evaluation we would rather set up a small slice of your genuine data than have you poke at a demo account.

Question 6

What comes across from our existing tools?

Accepted Answer

Clients, contacts, deals and their history from the CRM; projects, tasks and hours from the project tool; invoices, ledger and contacts from accounting; and the spreadsheets, which are usually where the real business logic is hiding. It arrives as structured records, not as attachments.

Question 7

What happens to five years of history?

Accepted Answer

It comes with you as records rather than a PDF archive, which means it stays searchable - and Q uses it when drafting proposals for comparable work. History is one of the main reasons the system gets useful in month two rather than month six.

Question 8

Can we get our data out again?

Accepted Answer

Any time, in full, in formats you can actually use - plus a REST API and webhooks across every module. If leaving is hard, the "you own your data" claim is marketing. We would rather you never test it, but you can.

Question 9

What if the migration goes wrong?

Accepted Answer

That is what the parallel week is for: both systems running, you checking BOS against records you already trust. Nothing is switched off until you say the numbers match. If they never match, you have lost a month and no data.

Question 10

We have data in a system with no API. Now what?

Accepted Answer

Managed Services builds connectors to whatever you run, including internal systems and industry software with no public interface. If it has a database, it can be reached - and if it genuinely cannot, we will say so.

Question 11

What does it cost?

Accepted Answer

Launch is free forever for one user. Run is $37 per user per month and Scale is $64, both on annual billing - $44 and $77 if you pay monthly. Both carry founding pricing, locked in for as long as you stay. Managed Services is priced on volume rather than headcount.

Question 12

Can we end up owning it outright?

Accepted Answer

Yes, and it is a deliberate route rather than an exception. We build, we train your team, we co-build alongside them, and you take over at whatever pace suits you - build, maintenance and support included if you want them. What remains at that point is a licence for the platform underneath rather than a per-seat bill. Most businesses stop partway, at the rung where they can customise without us.

Question 13

We already pay for these tools. Why add another bill?

Accepted Answer

You are not adding one - you are replacing about six. The stack BOS replaces runs roughly $153 per user per month at list price, against $37 for Run. And you also pay someone to keep those six tools agreeing with each other, which never appears on any invoice and is usually the larger number.

Question 14

Is founding pricing a discount that expires?

Accepted Answer

No. It is locked for as long as you stay on the plan. If we raise list prices - and we will - you keep the rate you signed at. If you leave and come back, you come back at whatever the price is then.

Question 15

Do we pay for modules we do not use?

Accepted Answer

Pricing is per seat, not per module, so turning a module on costs nothing extra within your plan. The plan boundary is which modules are included at all, which is on the pricing page.

Question 16

What about part-time people and contractors?

Accepted Answer

They need a seat if they work in the system. Most firms give contractors scoped access for the duration of an engagement and release the seat afterwards, which is billed monthly rather than annually.

Question 17

What actually makes this different from a suite?

Accepted Answer

A suite is separate products behind one login, syncing overnight. BOS is one data model that every module reads and writes - the deal, the project and the invoice are the same object at different stages. There is nothing to sync, so there is no integration to break.

Question 18

Which tools do we cancel?

Accepted Answer

The ones whose job is holding your business together: project tools, CRM, the spreadsheet sprawl standing in for finance and goals, marketing tools, automation glue and BI dashboards. The ones with a real job of their own - email, accounting, banking, design files, identity - connect and stay.

Question 19

Does it integrate with Slack, Google Workspace, Xero?

Accepted Answer

Yes to all three. Email and calendar, accounting, banking feeds, identity providers and design tools connect natively. Slack and Teams receive notifications; they do not need to become your filing system any more.

Question 20

Can we use just one module?

Accepted Answer

You can, and it will be a decent tool. It will also be the least interesting version of this - the argument for BOS is the thread between modules, so a single module is best treated as a way in rather than a destination.

Question 21

Can it be customised for how we work?

Accepted Answer

Configuration covers most of it. Beyond that, Managed Services builds custom modules, workflows and connectors for a dedicated deployment - that is the route when the fit has to be exact rather than close.

Question 22

What if we need something that is not a module yet?

Accepted Answer

Managed Services builds it. There are live bespoke implementations running today: a Virtual Data Room for transaction and due-diligence document control, Manufacturing Planning for production scheduling and capacity, WhatsApp communications so client conversations land on the record, website management (WCMS) driven by the same content and brand records as your marketing, and OpenClaw / Hermes for agent management - standing up a swarm of digital employees alongside your human team. Bespoke modules sit on the same data model as the rest, so they thread rather than bolt on.

Question 23

What about hubs, activity and knowledge - are those extra?

Accepted Answer

No. They are the platform layer underneath every module: hubs gather everything about one client or entity, activity is the single audit and notification stream, knowledge holds what your business already knows so Q can read it. They come with the system.

Question 24

Will Q do things without asking?

Accepted Answer

No. Q drafts, chases, flags and prepares - and stops. Everything it has prepared sits in the act queue waiting on a person, it has no payment authority, and every action it takes is written to the activity stream with a timestamp you can read.

Question 25

Is our data used to train AI models?

Accepted Answer

Never. What your team types and what Q writes does not train any model, ours or a third party's. This is contractual rather than a setting you have to find, and it does not change on any plan.

Question 26

How do we know Q is not making things up?

Accepted Answer

Every answer cites the records it read, and you can open them. When it cannot source something it says so rather than filling the gap - you will see "I could not find" more often than you might expect from an AI product, which is deliberate.

Question 27

Can Q see things a person should not?

Accepted Answer

No. Q inherits the permissions of whoever is asking, always. A consultant walled off from another client gets an answer that genuinely does not include that client - the boundary is enforced in the data layer, not by hiding it on screen.

Question 28

Can we run it without sending data to a cloud model?

Accepted Answer

Yes, under Managed Services, with local model inference so nothing leaves your network. On the standard cloud plans, model calls go to our providers under agreements that forbid training on your data.

Question 29

Will AI-written content sound generic?

Accepted Answer

It writes to your brand voice record, so the first draft is in your tone rather than in the internet's. It is a starting point, not a replacement - your people still write. What goes away is the two rounds of amends spent recovering the voice.

Question 30

Where is our data hosted?

Accepted Answer

Singapore by default. Under Managed Services we deploy into your own cloud account or your data centre where residency rules require it - the options are on the trust section rather than buried in a contract.

Question 31

Are you SOC 2 or ISO 27001 certified?

Accepted Answer

Not yet, and we will not put the badge on the site until we are. Both are underway. We will send you the current control documentation, and we would rather lose a deal to that answer than win one by overstating it.

Question 32

What compliance can you claim today?

Accepted Answer

Singapore PDPA and GDPR, with the data processing agreement available before you sign and the sub-processor list published. SSO and SAML, record-level permissions, and an audit log on every action with retention you configure.

Question 33

How do client confidentiality walls work?

Accepted Answer

Access attaches to records and hubs rather than to screens, so two teams on competing clients cannot see each other in search, reports or Q. Because it is enforced in the data layer, it holds for the API too.

Question 34

Who at UseKase can see our data?

Accepted Answer

A small named group, under access controls, only when supporting you and with the access logged. We do not browse customer data, and support access can be gated behind your approval on managed deployments.

Question 35

What is your uptime and backup position?

Accepted Answer

Continuous backups with point-in-time recovery, and status reporting for cloud customers. We publish our real numbers rather than a target - ask on the call and we will show you the current figures rather than a marketing SLA.

Question 36

What is the difference between cloud and managed?

Accepted Answer

Cloud is our infrastructure, self-serve, live in weeks, priced per seat. Managed Services is a dedicated BOS we build and run for you - in our cloud, your cloud or your data centre - with custom modules and connectors, priced on volume.

Question 37

Can it run entirely inside our network?

Accepted Answer

Yes, on-premise under Managed Services, including local model inference so no data leaves your network at all. This is the route for regulated environments and groups with an existing estate.

Question 38

Do we need IT people to run it?

Accepted Answer

On cloud, no - we handle updates, security and uptime. On a managed deployment you need someone who can grant us access to your cloud account; the running is still ours.

Question 39

Can we start on cloud and move to managed later?

Accepted Answer

Yes, and it is a common path - start self-serve, move when procurement or residency requires it. The data moves with you; it is the same system.

Question 40

Who is behind BOS?

Accepted Answer

UseKase, based in Singapore. We build BOS and we run our own business on it - the numbers on the homepage about savings and Q's work are ours, measured on our own deployment, not a customer case study we borrowed.

Question 41

You are young. What if you fail?

Accepted Answer

A fair question that most vendors dodge. Your data is exportable in full at any time, in usable formats, with an open API - so the failure mode is an inconvenient migration rather than a hostage situation. For managed deployments running in your own cloud, the system keeps running regardless.

Question 42

Do you have customers like us?

Accepted Answer

Probably, and we will tell you honestly if not. Our published stories are anonymised at the customers' request, with their real figures. If you want a reference call rather than a story, ask - we will arrange one where we can.

Question 43

Do you work with partners or resellers?

Accepted Answer

Yes - client partners with category exclusivity, sector co-builds where we package your template, and co-investment. These are real arrangements rather than a partner page, and they start with a conversation.

Question 44

What is the startup program?

Accepted Answer

Six months of BOS free for startups in a partnering incubator, at a university, or with institutional funding. It exists because early teams are the ones most damaged by a fragmented stack and least able to pay for the fix.

The awkward ones, answered first.

{{ g.label }}

Not in the standard product.

Ask the people who built it.