Choose one repeatable outcome
A broad promise to “automate the business” is hard to scope and harder to accept. Choose a specific process with identifiable inputs and outputs: turn an approved form submission into a validated CRM record, or prepare a monthly reporting draft for review.
Ask who owns the process today, how exceptions are handled, and what a successful handoff looks like. If nobody can explain the existing decision rules, discovery is part of the project rather than an inconvenience to skip.
THE WORKING SEQUENCE
- 01Define the input
- 02Test the exceptions
- 03Document the handoff
Package the boundaries
Describe the included systems, data fields, trigger frequency, and expected review steps. Name the exclusions. A lead workflow may include a single form and CRM pipeline; additional sources, historical cleanup, or new sales logic can be separately scoped.
Define acceptance with examples. The client should know which test records will be used, what output is expected, and who approves the result. Avoid defining success solely as “the automation runs” when the real requirement is correct data and a usable process.
Price the work you can explain
Separate discovery, build, testing, documentation, and handoff. Account for dependencies such as credential access and client feedback. If you propose ongoing support, define response expectations and the types of changes included.
Illustrative project pricing is a planning input, not an earnings claim. Your scope, market, delivery costs, and positioning determine whether a particular price is viable. Check the effort and risk before presenting a package.
Make the handoff part of the product
Provide an operating guide, a list of owners, tested examples, and a clear pause procedure. Explain what a failed run looks like and where to find useful evidence. Agree who monitors the system after launch.
A blueprint can give you a documented starting structure. Your service adds the client-specific decisions, configuration, validation, and accountability that make it usable in a real business. Keep those responsibilities explicit in both the proposal and delivery process.
Put the method to work. Explore the n8n automation blueprints in the Stems Agency Vault.