Sell the Result, Then Document the Scope

Clients buy a working business process. Describe the result in plain language, then make the implementation and acceptance boundary specific.

SchemaBounce records the automation, price, publisher, buyer and purchase lifecycle. It does not decide whether a client's business outcome was met. Put the acceptance check in your client agreement and your listing description.

Write the offer

An offer answers six questions before the client pays.

Question	What to write
Result	The process that works when delivery is complete.
Inputs	The client systems, accounts and data the workflow needs.
Acceptance	A repeatable test with an expected result.
Exclusions	Migration, cleanup, content or vendor work outside the price.
Handoff	Documentation, training and ownership after acceptance.
Support	A link to a separate maintenance plan, if you offer one.

Fixed implementation, separate maintenance

The first market cell sells a fixed one-time implementation, followed by an optional monthly maintenance subscription priced on its own (dec-008). New sources, jurisdictions, message families or bulk migration need a change order. State that in the offer.

Choose the commercial path

• Public listing for a repeatable automation with the same core deliverable across clients.
• Proposal on a buyer request for a named buyer and a specific scope. See Requests and proposals.
• Managed listing when buyers pay for continuing product releases, not for an open-ended support promise.
• Maintenance plan for response time, included change minutes and recurring service coverage. See Maintenance subscriptions.

Check your margin

Price from the value and the delivery risk, then compare it with your recorded labor, runtime, API and subcontractor costs. The Seller Hub margin view only includes costs you record. Marketplace take-home is before your own costs. See Earnings and fees.

Related

• Listing types and pricing
• Clients, handover and support