Know what is built.
Know what happens next.

The business keeps ownership of its domain. Code handoff and ownership of custom deliverables are defined in the written agreement, subject to payment and any licensed third-party assets.

The first payment is requested only after the written scope is accepted. Milestones, revision rounds, outside costs, final payment, and launch or handoff conditions are stated before work begins.

Yes. A focused first release can expand after the original scope is delivered and verified. New pages, workflows, integrations, or software features receive a separate written scope instead of silently changing the agreement.

The written plan can include custom responsive page types, clear service positioning, proof, accessibility-aware interaction, a guided enquiry backend, metadata, structured data, sitemap, performance basics, TLS deployment, and launch checks. The exact list depends on the approved scope.

No. It gives search engines a technically clear site through unique page titles and descriptions, semantic content, internal links, structured data, sitemap, and performance work. Competition, authority, location, reviews, links, and ongoing content still affect results.

Yes, when included. GA4 is configured with the agreed consent behavior and useful conversion events, while Search Console is connected to a client-owned Google account. Collection and indexing are tested on the production hostname.

Yes, as custom software scope. Technical discovery defines the users, permissions, data model, workflows, API contracts, integrations, hosting, monitoring, recovery needs, and acceptance tests before a quote is confirmed.

Only after confirming that the product offers a documented, permitted API or a reliable export. Integration feasibility, data rights, rate limits, authentication, vendor costs, and failure behavior are assessed before any promise is made.

No. A static marketing site may not need a database at all. PostgreSQL, migrations, constraints, and row-level security are used only where the selected application and data model benefit from them. When included, access policies are tested directly.

No. Use limited authorization, invite appropriately scoped access, or add exact DNS records yourself during a guided session. Do not send account passwords or private API keys through email or a public form.

When the product contains private data, the backend must enforce identity, role, ownership, and tenant boundaries on every protected request. Testing includes logged-out URL reuse, direct API access, changed IDs, expired sessions, and cross-user attempts.

The launch record identifies domain, analytics, source, deployment, backup, monitoring, and support responsibilities. Code handoff is available, and an optional care plan can be selected in writing. Continued service does not start as a surprise subscription.