← Denton BBQ

DENTON BBQ / STANDARD OPERATING PROCEDURE

A clear path to client independence.

Our Project Handoff SOP gives every client a documented option to operate their project independently, appoint another technology provider, or own their infrastructure while retaining Denton BBQ for optional development and support.

All projectsNo hosting-plan requirement
Client controlOwn provider accounts and billing
Verified handoffTest, accept and document the change

CHOOSE YOUR OPERATING MODEL

Three options, one standard

The path applies to every Denton BBQ project, including projects not subscribed to managed hosting. The detailed scope depends on the project agreement, software licenses and provider capabilities.

Client self-managed

The client assumes ongoing hosting, infrastructure costs, administration and operations after a completed handoff.

Successor technology provider

A client-authorized IT team or developer takes over with documented access, environment setup, working integrations and operational runbooks.

Client-owned, DBBQ-supported

The client controls production accounts and billing; Denton BBQ continues development or support only under the agreed arrangement.

DBBQ-SOP-001

Six-phase project handoff

1. Authorize & scope

Identify the client's authorized decision-maker, destination provider, assets, contractual rights, acceptance criteria, schedule and any agreed transition work.

2. Inventory & classify

Document each application, domain, repository, database, identity provider, storage service, communication channel and integration. Distinguish client-owned, transferable, migratable and DBBQ-internal assets.

3. Establish client control

Verify client-controlled provider accounts, billing, named administrators and recovery contacts. Set up independent environments, appropriate access and new scoped credentials.

4. Transfer or reconfigure

Use an approved provider transfer where supported or move agreed deliverables and data to client-owned infrastructure. Reconnect deployments, domains, authentication, storage and integrations.

5. Validate and cut over

Test critical business operations, security, records, communications, external connections and recovery. Obtain approval for production cutover and record results.

6. Accept and close

Deliver technical runbooks and the asset inventory, record written acceptance, resolve access and recurring billing, and agree on any remaining DBBQ support.

INVENTORY & DEPENDENCIES

More than handing over code

The project-specific handoff plan includes all agreed operational dependencies. Where a provider cannot transfer ownership directly, the plan documents an alternative migration or reconfiguration.

Code & deployments

Source, build/deploy instructions, hosting, project settings and environments

Database & files

Project records, schemas, attachments, storage permissions, recovery and verification

Identity & access

Logins, organization permissions, administrative access and sign-in continuity

Domains & communications

DNS, SSL, email, SMS, forms, webhooks and routing

Operational integrations

Client-controlled software connections, API credentials, scheduled jobs and monitoring

Documentation & billing

Runbooks, third-party costs, licensing constraints, acceptance and successor contacts

EXISTING CLIENT-OWNED PLATFORMS

Kintone stays with its client

Denton BBQ does not transfer a Kintone account or stack as part of a project handoff. For client-owned Kintone systems, including CP Machine and OFP, the client already manages its own Kintone subscription, applications and data.

What stays unchanged

The client's existing Kintone accounts, applications, records, attachments, permissions and subscriptions remain under that client's administration.

What we verify

Any DBBQ-built website or portal connection to Kintone is documented, reconfigured if necessary and tested with client-authorized credentials during a hosting or application transition.

Kintone data export or account migration is not a default part of DBBQ's handoff scope. Any Kintone-side changes would require separate written agreement and the client's authorization.

CONTINUITY & CLOSEOUT

Complete only after client acceptance

Before handoff closes, we verify client administrative and billing control, independent deployment, core workflows, project data and files, authentication, connected services, and backup or recovery arrangements. Known exceptions and outstanding work are documented and acknowledged.

Transition labor, vendor subscriptions, license rights, retention and termination dates are governed by the applicable signed agreement. The SOP is an operational standard, not an assignment of IP rights or a guarantee of zero downtime. DBBQ internal billing/support systems and unrelated clients' resources do not transfer automatically.

DBBQ-SOP-001 · Project Handoff & Client Independence · Version 1.0. Each project requires its own scope, inventory, test record and written client acceptance.