Skip to main content

Clients, Handover and Support for Builders

The client's workspace and data belong to the client (dec-015). Your relationship with the client belongs to you (dec-013, dec-016). This page covers how those two facts work together.

Ownership​

  • You sell the automation. The buyer installs it in their own workspace.
  • The buyer connects their own accounts. You never hold their credentials.
  • Run proof from a one-time sale reaches you only if the buyer shares it. See Requests and proposals.

Access to a client workspace​

  • You can operate only on deployments where the buyer granted access.
  • Operation sessions are scoped and time-limited.
  • A change you want to make goes back to the buyer as a proposal for review before anything is changed.
  • A paid maintenance plan records service coverage. It does not grant access. See Maintenance subscriptions.

To operate a customer workspace from your own MCP client, see Hosted MCP.

Handover​

Handover means the client keeps running and controlling what you built, with you no longer in the loop.

  • A one-time purchase is already a handover. The buyer owns a copy that runs in their workspace, with no updates or support (dec-013).
  • A subscription adds updates and support. When it ends, the entitlement ends. See Payouts, refunds and disputes.
  • Put documentation, training and ownership after acceptance in your listing description or proposal.

Support and escalation​

  • You answer your subscribers' questions about what your automation does.
  • Response time on a maintenance plan is a response commitment, not a guaranteed resolution time.
  • Platform problems, takedown requests and license violations go to SchemaBounce. Handling is run by SchemaBounce.

Subcontracting​

You can record terms with another builder who delivers part of one engagement. This is not a reseller program. SchemaBounce has none (dec-015), and every builder sells under their own handle.

  • The lead builder proposes a fixed amount or a percentage for a named engagement and client workspace.
  • The other builder accepts. The agreement is kept as an immutable snapshot.
  • The agreement records payout terms between the two builders. It gives the second builder no access to the client workspace, does not deploy anything and does not replace your client contract.
  • Give one builder final responsibility for client communication and acceptance.
  • Record subcontractor costs in the Seller Hub so margin includes them.