Question 1

How do engagements typically start?

Accepted Answer

Most projects start with a short scoping call, followed by a fixed-price discovery phase (1–2 weeks) that produces a clear scope, timeline, and estimate for the build phase. For smaller, well-defined work we can skip straight to a proposal.

Question 2

Do you work with startups, or only established companies?

Accepted Answer

Both. We size the engagement model to fit: fixed-scope for startups validating an idea, dedicated teams for companies with an ongoing roadmap.

Question 3

How is pricing structured?

Accepted Answer

Three models: fixed scope for well-defined projects, a dedicated team on a monthly retainer for ongoing roadmaps, and hourly for smaller or exploratory work. See the Pricing page for details.

Question 4

Do you require a minimum contract length?

Accepted Answer

Fixed-scope projects have no minimum beyond the agreed timeline. Dedicated team engagements typically start with a one-month trial period before moving to a longer commitment.

Question 5

What does a typical project timeline look like?

Accepted Answer

A focused web or mobile app usually runs 10–18 weeks from discovery to launch. AI and automation projects often start with a 1–2 week feasibility spike before a full timeline is set.

Question 6

How involved do we need to be during the build?

Accepted Answer

We run in two-week sprints with a live demo at the end of each one. We expect a single point of contact on your side who can answer questions within a business day. Beyond that, involvement is as light or heavy as you'd like.

Question 7

What happens after launch?

Accepted Answer

Every project ships with a 30-day warranty window for bug fixes at no extra cost. After that, most clients move to a maintenance retainer or call on us ad hoc for new feature work.

Question 8

Who owns the code and infrastructure after the project ends?

Accepted Answer

You do, fully. Repositories live in your GitHub organization from day one, and infrastructure is provisioned under your own cloud accounts wherever possible.

Question 9

Can you work with our existing codebase and team?

Accepted Answer

Yes, a large share of our work is joining an existing codebase, either for a defined feature build or as embedded staff augmentation inside your team's own process.

Question 10

How do you handle data privacy, especially for AI projects?

Accepted Answer

We scope data handling requirements during discovery, including private model endpoints, VPC-hosted infrastructure, or self-hosted models where compliance requires it. NDAs are standard before any client data is shared.

Frequently asked questions

Engagement

Pricing

Process

Technical

Still have a question?