Question 1

How long does a typical engagement take?

Accepted Answer

Most engagements move from Discover to a live system in four to eight weeks, depending on scope — you'll get a specific timeline before any work begins, not a vague estimate.

Question 2

How is our data secured?

Accepted Answer

Your data stays within access-controlled systems scoped specifically to the automation we build. We don't request broader access than the engagement requires, and we're glad to work within your existing security review process.

Question 3

What if it doesn't work the way we need?

Accepted Answer

Every engagement starts with a Design stage specifically so we catch mismatches before any code is written. If something still isn't right after launch, that's what Support is for — not an extra invoice.

Question 4

How big is your team?

Accepted Answer

Small and senior, by design — every engagement is handled by people who've actually built systems like yours before, not routed through a large account-management layer.

Question 5

What happens after launch?

Accepted Answer

We stay involved. A system nobody maintains slowly stops working, and we'd rather prevent that than get an emergency call six months from now.

Question 6

Do we need our own technical team to work with you?

Accepted Answer

No — we work directly with whoever runs the process day to day. If you have technical staff, we're glad to loop them in; if you don't, that's normal too.

Question 7

Do you charge a fixed price, or bill hourly?

Accepted Answer

Fixed, scope-based pricing agreed before work begins — see the Pricing page for how engagements get scoped. We don't bill open-ended hours against a project.

Question 8

Do we own what you build?

Accepted Answer

Yes. What we build for you is yours — this isn't a platform you rent access to, and there's no vendor lock-in by design.

Question 9

What industries do you actually work with?

Accepted Answer

Real estate, medical, legal, manufacturing, education, finance, and e-commerce most often — see the Industries page for how the approach differs by vertical. The underlying patterns generalize well beyond that list too.

Question 10

Is this really custom, or a template with our logo on it?

Accepted Answer

Custom. Discover and Design exist specifically to map your actual workflow before anything is built — a template can't do that, because it's built before it knows what your business needs.

Question 11

What happens if we want to stop working together?

Accepted Answer

You keep what was built. There's no penalty for ending an engagement, and because you own the system outright, walking away doesn't mean losing what you paid for.

Question 12

Can you work with the specific tools we already use?

Accepted Answer

Usually, yes — Custom Integrations exists precisely for this. If a tool has any way to connect to it (an API, a data export, even email), it's very likely workable.

The objections you haven't voiced yet