Frequently Asked
About AI systems and software development: how we scope and price work, how often you see something running, who owns what at the end, and what happens to your data along the way.
AI systems and custom software: AI agents and workflow automation, web applications, iOS, Android, macOS, and Windows. Most engagements combine several of those, because a mobile app usually needs a backend and an agent usually needs somewhere for your team to review what it did.
Fixed scope, fixed price, split across milestones, and quoted after the scoping call rather than before it. We do not bill hourly, so a slower week is our problem rather than your invoice. Anything you add mid-build is quoted separately before we start on it.
From around three weeks for a marketing site to sixteen for a full mobile or SaaS product. An AI agent adapted from one we have already built is usually one to three weeks. The scoping call narrows that range to a date.
Every two weeks, as working software rather than a status report: a preview URL for web builds, a TestFlight or internal-track build for mobile. If a milestone is at risk you hear it in that cycle, not at the deadline.
You do, from day one. Repositories, cloud accounts, app store listings, and API keys are created under your ownership and we work inside them. There is no proprietary layer you would have to license later, and nothing preventing another team from picking the work up.
Every system gets the narrowest data access it needs to do its job. We use API tiers where your inputs are not used to train the provider models, can deploy inside your own cloud account where that is a requirement, and will sign an NDA or DPA before we see anything sensitive.
We assume it will. Every system ships with confidence thresholds, validation on structured outputs, and a defined escalation path to a person. That failure behaviour is agreed with you during design, and the logs let us trace exactly what happened rather than guess.
Your choice. Keep us on a monthly retainer for iteration, monitoring, and platform upgrades, or take it in-house with documented code and a handover session for your team. Ongoing support is never a condition of the build.
Often, yes. We begin with a short paid audit of the code, the architecture, and the release pipeline, then give you the options honestly, including the case where a rebuild costs less than continuing. You are not committing to the full engagement to get that answer.
Send a short description of the bottleneck or the product through the contact form, or message us on WhatsApp. We follow up to arrange a scoping call, and you leave that call with an approach, a timeline, and a price. There is no charge for it and no obligation to proceed.
