The questions you would rather not ask.
These are the objections that come up on calls. Writing them down is cheaper for both of us than making you raise them politely.
You have no customers you can name.
Correct. We have engagements, they are under agreements that do not let us name them, and we would ask before naming anyone regardless. So there are no logos here.
What we offer instead: working software you can operate yourself before you speak to us, and a first step small enough that you are not betting anything on our reputation. If a named reference is a hard requirement for you, say so on the call and we will tell you honestly whether we can meet it yet.
You are two people.
We are. Glenn runs the commercial side, Joseph builds. There is no third person to escalate to and no account manager between you and the work.
The upside is that the person who answers your question is the person who wrote the code. The downside is capacity, and it is a real one: we take on few engagements at a time, and if we are full we will say so rather than stretch. Ask what else is running before you plan around us.
What happens when it gets a policy number wrong?
It will, eventually. Any system reading messy human input will. The question worth asking is what happens next, and the answer has to be structural rather than a promise.
A value that cannot be traced to a specific moment in the source does not get filled in. It gets flagged and left empty, because an empty field is a task and a confidently wrong one is a liability. A person approves before anything reaches a system of record. Our guide on provenance rather than generation explains the mechanism, and it includes a test you can run in anyone's demo, including ours.
What happens to our data?
It stays in your accounts. We work from copies rather than inside your live systems, and read-only wherever read-only will do.
What we do not have: SOC 2, ISO 27001, or any certification, and we are not going to imply otherwise. The security page describes how the system is designed and names the public standards it follows, then stops. The privacy notice says exactly what this website collects and how long it is kept. If your vendor review needs a questionnaire completed, send it and we will complete it.
What if you fold?
Fair question for a young company, and the honest answer is not "we will not".
It is that the design limits the damage. It runs on your accounts and your systems, it does not become the system of record, and turning it off leaves your CRM, your AMS and your policy system exactly as they were. You would lose the automation, not your data and not your operation. Ask us to walk through the specific shutdown path for whatever we would build for you, before you sign.
Is this a wrapper on a language model?
There is a model in it, and pretending otherwise would be silly. The part that takes the work is everything around it: connecting the systems you already run, deciding which values are trustworthy enough to fill in, holding the approval gate, and making the output land in the right field of the right record.
A useful way to judge any vendor here, us included: ask what the system does when it is unsure. A wrapper answers anyway.
How long before we see anything?
We start with a paid diagnosis on your own numbers, and you keep the plan whether or not we build. What we will not do is quote you a payback period. We have not run enough engagements to put a number on that which we would stand behind, and a figure invented to close a deal is the thing you would hold against us later.
Ask on the call and we will tell you what we think the first piece is and roughly what it involves.
Do you sell insurance?
No. We are not an insurance producer and we do not quote, place or bind coverage. Where an engagement touches regulated insurance work, a licensed party does that part. We do the orchestration around it.
The same applies to advice. Pages here that discuss recording consent, regulatory guidance or record-keeping are general education, and your counsel outranks them.
Something we have not answered?
Ask Glenn on (917) 207-1968 or Joseph on (747) 745-5837. If the answer is "we do not know yet", that is what you will get.
Still deciding?
Twenty minutes on your own systems. You leave with the map either way.