Do I need a complete specification?

No. Bring the current situation, who it affects, what is not working, and what a useful result would change. Discovery can turn that into a scope without pretending every unknown is already answered.

Can you work on an existing system?

Yes. Existing work normally begins with access, backups, source, hosting, data, integrations, and deployment. We avoid a rewrite decision until the system has been inspected.

Who owns the finished work?

Ownership and licensing are written into the agreement. Client-controlled domains, hosting, repositories, analytics, and vendor accounts are preferred when practical so access does not depend on one provider.

How are price and timing determined?

They depend on scope, uncertainty, integrations, content, data, review availability, and launch constraints. A short paid discovery or audit may be the responsible first step when an exact build estimate would otherwise be guesswork.

What happens after launch?

That is decided before launch. Options can include a defined correction period, maintenance, monitoring, updates, support hours, future feature work, or a documented handoff to another team.

Can you take a smaller project?

Yes. A smaller job works best when the question, access, expected result, and stopping point are clear.