Start with one repeatable step

Workflow improvements

Still repeating the same task by hand? Start with a $49 USD workflow plan or, when the fit is already clear, a $149 USD simple automation pilot. We map the work, test agreed failure cases, and leave approvals and live enablement under your control.

$49 USD
Workflow planOne recurring task · Current setup across up to 2 apps · Up to 3-page map · Build recommendation · One preference revision
$149 USD
Simple automation pilotOne flow · Trigger + up to 4 actions or transformations · Up to 2 connected apps · Built-in app connections · Tests, recovery, handover + one preference revision
Custom quote
Broader workflow or custom toolAdditional apps, branches, custom connections, higher-risk actions, monitoring, or continuing maintenance scoped separately
Discuss workflow improvements

Confirm the scope and price first · Approve the finished work before paying

At a glance

Useful when
You keep copying, renaming, or checking the same files by hand.
What you receive
Choose a written workflow plan or a simple automation pilot with test results, recovery notes, and handover instructions.
Choosing the right service
Choose the $49 plan to work out the steps before building. The $149 pilot builds one accepted simple workflow. For form submissions, see the intake pilot. For written instructions, see process documentation.

What a small project can include

  • Workflow plan: a map of one recurring task and its current setup, covering up to two apps and up to three pages. It records inputs, outputs, permissions, approvals, likely failures, the manual fallback, and a recommendation on whether to build.
  • Simple automation pilot: one flow with one trigger and up to four actions or transformations across up to two connected apps—a maximum of five steps total—using built-in connections supported by the selected apps.
  • Testing and recovery: expected results for normal, duplicate, incomplete, and destination-failure cases, plus a visible way to identify a failed run and return to the manual process.
  • Handover: run instructions, known limits, the maintenance owner, and the point at which the workflow should stop or be reviewed.

The written scope states whether setup, live enablement, monitoring, updates, or continuing support are included. Ongoing maintenance is included only when the written scope says so.

Scope and limits

The $49 USD workflow plan covers one recurring task and its current setup, up to two apps, and a workflow map of up to three pages. It documents permissions, approvals, likely failures, the manual fallback, and a recommendation on whether to build. It includes one consolidated in-scope preference revision. The plan does not include account access, setup, a working automation, or changes to a live system.

If you accept a build of $149 USD or more for the same agreed task within 60 calendar days after the plan is delivered, the $49 USD plan fee is credited once toward that build. The accepted build quote is reduced by $49 USD, so the plan and a qualifying $149 USD simple pilot cost $149 USD in total. The credit does not transfer to a different task or apply more than once.

The $149 USD simple automation pilot covers one flow of up to five steps and up to two connected apps using built-in connections supported by the selected apps. For this package, each trigger, action, or transformation counts as one step, and the trigger is included in the five-step total. It includes the normal, duplicate, incomplete, and destination-failure tests described above; recovery notes; handover instructions; and one consolidated in-scope preference revision.

A consolidated preference revision is one collected request to adjust the delivered work within the accepted task, trigger, steps, apps, connectors, test cases, and output. A new task, app, trigger, branch, or outcome is new scope. Covered corrections under the 30-day corrections guarantee are separate and do not use the preference revision.

The fixed pilot does not include custom APIs, webhooks, conditional branches, payment steps, third-party subscription or usage fees, sensitive-data or sensitive-decision workflows, autonomous outbound sends, ongoing monitoring, or continuing maintenance. Broader workflows and custom tools are quoted separately after review.

Buying a plan or pilot does not authorize access to an account or changes to a live system. Live enablement requires separate explicit permission, agreed access, a named approver, and a recorded fallback. Credentials and tokens must use the transfer method agreed for the project and should never be sent in the initial inquiry.

We confirm the accepted scope and delivery date in writing before work starts. You review and approve the finished work before paying. Final editable files and handover materials follow confirmed payment. Payment takes place on a hosted Stripe invoice after approval; this website does not collect card details.

Where to look first

Look for tasks with clear starting information, a rule someone can explain, and a result you can check. Examples to assess include reshaping a repeated export, preparing a recurring exception list, or applying an agreed naming pattern to working copies of files.

Support for a particular platform or integration needs to be checked first. A checklist, template, or simpler manual process may be the more practical outcome.

If the process changes every week, important decisions are undocumented, or no one can handle failures, clarify the process first. Also consider whether the task occurs often enough to justify build time, testing, subscriptions, review, and future changes.

A useful improvement should be understandable to the person who will run and maintain it. Some steps may still need a person to review them.

What to bring

  • A walkthrough of the current task and how often it occurs.
  • Representative inputs, the expected output, and examples of missing or unusual records.
  • The rules that determine the result and a reviewer who can resolve ambiguity.
  • The tools and environment involved, permitted access, and actions that must remain manual.
  • A named maintenance owner, likely changes, and what happens if the task fails.

Describe accounts and permissions without sending passwords, API keys, or tokens. Access requirements and any use of live systems must be reviewed separately.

See an example before deciding to build

The real NYC service-request snapshot shows source preservation, repeatable date checks, and a clearly dated status report. It is a prepared dataset, not a live integration.

Use the workflow decision guide to measure current effort and compare it with setup, review, failure handling, and maintenance.

Test what happens when something goes wrong

  • Test a normal case, a duplicate case, an incomplete case, and a destination failure against the agreed flow.
  • Show what completed, what failed, how the failure is made visible, and how to return to the manual process.
  • For any record-changing action, agree a safe test, recovery method, and protection against duplicate actions after a rerun.

Steps that need approval stay with the person authorized to give it. A passed test supports only the agreed cases and environment; it is not a guarantee that every future input or platform change will behave the same way.

Describe one recurring step

Share what triggers the task, its usual frequency, the apps involved, an example input and desired output, and the decisions it requires. Begin with a description or redacted example. We’ll confirm whether the $49 USD plan, the $149 USD simple pilot, or a custom scope fits, then agree on the delivery date.

Discuss a workflow improvement · Download the editable readiness checklist

Help opening these files

Select the file link, then check the page that opens or your Downloads folder.

PDF: read it in your browser. DOCX: edit it in Word or a compatible document app. XLSX or CSV: open it in a spreadsheet app. TXT: open it as plain text. You can read the example on this page without downloading anything.

If a file does not open, tell us the file name and what happened. Do not send private data in your first message.

Have a task in mind?

Start with the result you need.

Tell us what you need
Need help using this site?

New here? You do not need to know the service name. Tell us what you have now and what a useful finished result would look like.

  1. Start a short inquiry. A few sentences are enough, and no account or files are needed.
  2. Compare services, package prices, and quote options, or see complete public-source examples before you ask.
  3. Already working with Cleargrain? Use Client Login for private requests, files, messages, and project review.

Still unsure? Describe the result you need, including technical detail if useful. Larger spreadsheets and custom work are welcome; we’ll review the task before agreeing on the work and price.

What do the file types and technical terms mean?
PDF
A document you can read in a browser or PDF reader.
XLSX
An Excel workbook. Open it in a spreadsheet app to inspect the full example.
DOCX
An editable Word document. Open it in Word or another compatible document app.
CSV
A plain spreadsheet file. Open it in a spreadsheet app to see rows and columns.
TXT
A plain-text checklist or template. Open it in a text editor or copy its text.
SOP (standard operating procedure)
A step-by-step guide for a recurring task.
CRM (customer relationship management)
A system used to organize customer or contact records.
Workflow
The steps that move a task from start to finish.
Flat file
One table of rows and columns, with one header row.
Exception list
Records that need a decision or more information, with references to the original rows.
Source-ready procedure
A procedure written from approved material you already have, rather than from a supplied walkthrough.
Preference revision
One collected round of requested adjustments within the agreed work. Correcting work that fails the written scope is separate.
White-label support
Work prepared for your agency to review and present in its own branding.

To download a file, select its download link. It may open in your browser or appear in Downloads. If the browser asks, choose where to save it. Downloading an example does not place an order.