FAQ
The questions people actually ask.
Not the marketing-page kind. The real ones from real emails and real discovery calls, answered plainly.
Before we start
How do I know if my idea is a fit for Doyel Labs?
If your idea is a piece of software that ties an operation together — a marketing site, a payroll workspace, a portal, an integration, an internal tool, a custom program — we can probably build it. If you're not sure, send us a paragraph and we'll tell you either "yes, let's talk," "no, but here's who could," or "you don't need software for that, here's what you actually need." All three are honest answers.
Do you require a spec or a wireframe up front?
No. Most of our clients arrive with an idea, not a spec. A paragraph about the operation is enough to start a discovery call. We'll write the spec together during the scoping phase.
What size project do you typically take on?
Anywhere from a three-day marketing site to a multi-month custom program. We do not take on scope that will take longer than a quarter without breaking it into milestones — projects that run open-ended tend to lose their way.
Do you work with clients outside the United States?
Yes, though we're based in Wyoming (US Mountain time) and most of our clients are US-based. If your project has regulatory or compliance requirements outside the US, we'll tell you up front whether we're the right team for it.
Pricing and timelines
How is a project priced?
Fixed price, quoted after a short discovery call. We never bill hourly. If the scope grows, we requote. Every quote covers labor, cloud infrastructure we set up for you, and the AI tooling we use during the build.
How much does a typical project cost?
It depends heavily on scope. A small marketing site is very different from a compliance workspace. The fastest way to know is a short call — we can usually quote within one business day.
How fast can you deliver?
Marketing sites: three days for a small operator, one to two weeks for a richer build. Operator workspaces (payroll, internal tools): about a week for a first version. Larger programs: quoted by the sprint with a preview URL and a Loom every business day so you always know where the project stands.
Do you take a deposit?
Yes — 50% before we start on projects over $1,500, with the balance due at delivery (or against milestones for larger projects). Retainers are billed monthly, first month at signing.
Working together
How often will we hear from you during the build?
Every business day, minimum. A short Loom walkthrough of what's new, or an email with the preview URL. On larger projects, we set up a shared channel (Slack, email thread, or your preferred tool) so you never have to chase us.
Who do I actually talk to?
The person who's building your software. No handoff to an account manager, no ticket queue.
What if I want to change my mind mid-build?
Changes are expected. If the change fits inside the original scope, we absorb it. If it grows the scope, we requote — no silent creep, no surprise invoices.
What if we go dark for a week?
We check in. If you go dark longer than that, we pause the project (and pause billing on any active retainer) until you're back. Life happens.
After launch
Do you keep working on the software after it launches?
Yes, optionally. Every build comes with the option of a monthly retainer for maintenance, dependency updates, small new features, and a direct line for anything urgent. If you don't want the retainer, you own the source and can hand it to any engineer.
What if I want to fire you?
You can, at any time, for any reason. Source on your Git host, domain on your registrar, database on your cloud account. Everything transfers cleanly and any engineer can pick it up.
Do you support the software 24/7?
No. Retainers cover business-hours support (Mountain time), with a one-business-day response SLA. If your operation genuinely needs 24/7 on-call, we'll be honest about that being outside our current shape and help you find someone who does.
Trust and security
Who owns the code?
You do. Every line of it. It lives on your Git host from day one of the build.
Do you sign NDAs?
Yes, when the project involves proprietary information. Standard mutual NDA; we'll send a template or accept yours.
How do you handle sensitive data?
Local-first for anything that spends money — broker credentials for BAI stay on the operator's machine; bank details for payroll are never stored on our servers. Every product has a data map published on /security.
Are you insured?
We carry professional liability (Errors & Omissions) and cyber liability insurance. Certificate available on request.
Something not covered here? Send us the question — we'll answer, and if it's a question others might have, we'll add it here.