Who qualifies for the free pilot?
SaaS companies with fewer than 50 employees that operate their own browser-based product. You need real customer workflows to evaluate, a business owner, a technical contact who can help us install and test, and time for a fortnightly review. We confirm headcount, product fit, and launch capacity before accepting your application.
What is included in the pilot?
Setup, configuration, testing, supported features, normal AI use, maintenance of the agreed coverage, and founder support for the 60 days. We agree the rollout and the measurable outcomes before kickoff. Bespoke development outside that scope is scoped and priced separately.
When do the 60 days start, and can they be extended?
On your agreed go-live date, after setup and launch review. We record the start and end dates before launch: a pilot that goes live on November 16 runs to January 15, for example. If the agreed outcomes need more time, such as a seasonal task that has not come up yet, we can agree one 30-day extension.
Are the team inbox and Reports included?
Yes, where they are part of your agreed rollout. Inbox, triage, routing, and Reports are in preview and require integration and acceptance testing before activation. Your proposal confirms what will be available at launch. You can explore the sample experience in the demo.
What happens after the pilot?
We review the agreed outcomes with you before the pilot ends, and you choose whether to continue. Continuing means Core at US$1,000/month, or US$750/month at the founding rate, on a 12-month paid term. Nothing converts automatically: no paid subscription starts without your written agreement.
How does the founding rate work?
The first five eligible customers can continue at US$750/month, locked for the 12-month paid term. Eligibility and your rate are confirmed before setup. The free pilot is open to three SaaS teams; the founding rate is open to the first five eligible customers, with or without a pilot.
What do you need from our team?
A named business owner, a technical contact, test access, and a fortnightly review. Before launch, we agree the measurable outcomes the pilot is judged on, such as completed tasks, customer uptake, and the support effort that remains. Any public case study needs your separate permission.
Are there usage or workflow limits?
There is no fixed workflow count or conversation cap within the agreed coverage and normal use. We plan expected usage before kickoff. Significant usage changes and custom work are agreed first; there are no automatic overage charges.
What does setup involve?
We configure and test with your technical contact. In-product assistance typically takes two to four weeks, depending on access and integration complexity; preview feature timelines are confirmed separately. Your 60 days begin at agreed go-live.
We were offered three months. Does that still apply?
Yes. Pilots offered or agreed under the earlier three-month offer keep their three months.
Where does customer data go?
For the managed integration, approved requests are processed temporarily through Invocursor and OpenAI. Outcome metrics are separate from conversation records. Inbox and Reports require an agreed data flow before activation. See the privacy policy.