FAQ
Questions before we start.
Clear answers about fit, scope, delivery and working together.
Project fit
01What types of projects do you take on?
We focus on AI knowledge systems, workflow automation, AI products and SaaS, internal business tools, and selected mobile or strategy engagements. Fit depends on a clear business problem, realistic scope, available project ownership and budget—not a particular industry.
02What is the minimum project budget?
Projects typically start at US$5,000. Final pricing depends on scope, integrations, data requirements, user roles, timing and support. Smaller budgets may still be submitted, but the first scope may need to be narrower.
03Do you work with early-stage ideas?
Yes, when there is a clear problem, intended user and committed project owner. We can help shape an idea into a focused prototype or MVP, but discovery does not guarantee project acceptance or a particular business result.
04Can you improve an existing product?
Yes. We can review an existing product or workflow, identify practical improvements and work within the current architecture where appropriate. Access to the code, documentation and relevant systems is normally required before scope can be confirmed.
05Do you provide design as well as development?
Yes. Product structure, user flows, interface design and engineering can be scoped together. The proposal will state the exact design and development deliverables included.
06Can you integrate with existing tools and APIs?
Yes, where the required documentation, access and test environment are available. Feasibility is reviewed before commitment, and third-party fees, limits, availability and policy changes remain outside our control.
07Do you offer mobile app development?
We offer selected mobile companion apps, responsive web apps, API-connected iOS or Android interfaces and internal mobile tools. We will recommend a web or mobile approach based on the workflow and scope rather than defaulting to a native app.
Working together
01How do discovery calls work?
Discovery calls are arranged by email rather than through an online calendar. After reviewing your brief, we can suggest suitable times and use the call to clarify the workflow, users, constraints, scope and next steps.
02Do you sign NDAs?
Yes, an NDA can be arranged when appropriate. Please avoid sending passwords, private keys or highly sensitive material through the initial enquiry form.
03How are projects delivered?
Projects normally move through Discover, Define, Build, Test & Launch, followed by optional improvement work. Delivery uses written scope, milestone reviews, visible progress, documented decisions and an agreed handover.
04Do you provide ongoing support?
Optional support can cover maintenance, bug fixes, analytics review, feature iteration, model or prompt refinement and infrastructure improvements. Scope, availability and fees are agreed separately.
05Can you work across US, UK, Canada and Australia time zones?
Yes. We work remotely with async-friendly communication and written decisions, with Australia and APAC-friendly availability and planned overlap for other English-speaking markets. This does not imply a local office in each region.
Delivery and terms
01Do you guarantee business results?
No. We can agree technical deliverables and build toward defined goals, but revenue, adoption, cost savings and other commercial outcomes depend on factors outside our control. Any expected benefit remains a hypothesis until measured.
02Who owns the final source code?
Ownership is defined in the project agreement. Typically, agreed custom source code and deliverables transfer after the applicable payment milestones, subject to exclusions for pre-existing materials, open-source software, third-party services and licensed assets.
03What information should I prepare before submitting a project?
Prepare the business context, current workflow, intended users, main problem, desired outcome, existing tools and integrations, available data or documents, constraints, timeline, budget and decision-maker. Examples or screenshots help, but do not submit secrets or unnecessary sensitive personal data.
A considered first step
Have a question that depends on your project?
A project brief gives enough context to discuss fit, scope and the most useful next step.