Frequently asked questions

No. If an existing tool solves your problem well, we will recommend it. Custom work is for needs that existing products serve poorly.

Yes, after reviewing its structure and quality. We will tell you honestly if the foundation is sound enough to build on.

Established, well-supported tools. For web work that typically means TypeScript, a modern framework, and a relational database.

Ownership is agreed in the project terms; typically the delivered work belongs to the client.

Based on scope, features, integrations, data, and delivery requirements. We provide a written estimate rather than a flat price list.

Because project scope varies so much that fixed prices would be guesswork or misleading.

For a clearly described project, we can usually respond within a few working days.

Yes, but changes are agreed and estimated separately so the project stays honest.

A focused site can take a few weeks; larger sites with many sections and integrations take longer.

Applications are delivered in phases. Expect weeks to months depending on scope.

Content readiness and feedback delays, far more than technical issues.

Where those tools offer an API or a supported import/export method, usually yes. We will confirm before committing.

Yes, migration is a planned part of most projects and includes verification.

Through access control, encrypted connections, and careful handling. We do not overstate this as a formal guarantee.

Hosting is typically on reputable managed platforms. Hosting and third-party costs are usually separate and paid by you.

Yes, as a separate ongoing arrangement. Scope and response times depend on how critical the system is.

Yes. We document the system so another team can take it on if you prefer.

Fixes are handled according to the support arrangement, triaged by severity.