Question 1

We're a small program. Is this for us?

Accepted Answer

Small teams are exactly who this is for. The flagship engagement supports a statewide program run by a lean staff. The point of the work is widening what a small team can cover without adding headcount they don't have budget for.

Question 2

Will the AI make decisions about applicants?

Accepted Answer

No. Approvals, denials, exceptions, and anything else consequential stay with your team. We design that boundary in from the start and document it, so it survives audits and staff turnover.

Question 3

How do you keep AI answers accurate?

Accepted Answer

The AI answers from your own materials: internal documentation, website language, and program rules, and your team tests and tunes it before it ever faces the public. It does not improvise policy. When a question falls outside what it knows, saying 'let me connect you with the team' is the designed behavior. Output is monitored after launch, not just tested before it.

Question 4

What about our community's data?

Accepted Answer

Data handling is governed by a written policy: what is collected, where it lives, who can see it, and when it is deleted. We map the architecture to your legal obligations, including California privacy requirements, before anything goes live.

Question 5

Do callers know they're talking to AI?

Accepted Answer

Yes. Disclosure is required by California law and it is the honest thing to do. In practice it does not hurt adoption: people care that they got help at 9pm in their language, not that software answered.

Question 6

We're not in California. Do you work with programs in other states?

Accepted Answer

Yes. We build to your state's privacy and AI disclosure obligations, whatever they are. California is where the flagship runs, and its rules are among the strictest in the country.

Question 7

What does an engagement cost?

Accepted Answer

It depends on the gap we're closing, so the first conversation is free and ends with a scope you can take to your board. Engagements start with the smallest build that closes your most important gap, so you see it working before you commit to more. And if the answer is a process fix instead of AI, we will tell you, and you will have spent nothing.

Question 8

How long before something is live?

Accepted Answer

It depends on the gap, so we will not pretend there is one number. We build the smallest system that closes your most important gap first, prove it with your team against real scenarios, then expand. The first call ends with a scope, and the scope includes a timeline.

Question 9

What happens when the engagement ends?

Accepted Answer

You keep everything: documentation, configurations, and the knowledge to run what was built. We can stay on to operate it, or hand it off cleanly. No lock-in by obscurity.

Question 10

Why not a big firm?

Accepted Answer

You get the architect, not a logo and a rotating bench. The person who scopes your system designs it, builds it, and answers for it.

Frequently Asked Questions