Cleargrain DocsSpreadsheets · Instructions · Research
Menu
Start a project
Need help using this site?

Start with what you need. Describe the problem and what you want to make easier. You can send a short inquiry without an account.

  1. Browse services and prices, or go straight to tell us what you need.
  2. Examples show spreadsheet, procedure, and research projects made with public sources. They are independent projects, not paid client work. You can read them without downloading anything.
  3. Use Client Login for private requests, files, and project review. Start with the no-account inquiry form; no files are needed.

Have a complex or technical project? Describe it here. The listed packages are starting points. Larger spreadsheets are welcome; we review what is practical, the size, and the complexity before agreeing 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 or procedure
Step-by-step instructions for a task.
CRM
An app used to organize customer or contact records.
Workflow
The steps that move a task from start to finish.

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.

Secondary service · accepting fit inquiries

One small bug.
A fix your developer can review.

For small teams and agencies with a reproducible issue waiting in the backlog and a developer who can review the change. Start with a description of the problem.

$99 USD
Introductory small-bug pilotOne low-risk defect, only if it fits the agreed scope. Free fit screening comes first.
Ask if my bug fits

No account, files, or payment needed to ask. Approve the finished work before paying.

What makes a good fit?

A small, isolated display, formatting, or non-sensitive application-behavior defect that can be reproduced in a safe test environment. You own the code or have permission to request changes, and your developer can check the proposed patch.

The free fit check reviews your description for suitability. Diagnosis and repair work start only after we agree the scope, price, timing, and verification arrangements in writing. If the issue is larger or unsuitable, we may offer a separate quote or decline it. An inquiry does not reserve a repair or guarantee acceptance.

What we would agree to deliver

  • A diagnosis of the one agreed defect and a proposed patch.
  • A before-and-after reproduction or regression test, with evidence of the checks actually run.
  • A plain-language explanation of the change, its limits, and anything left untested.
  • Review and handover instructions for your developer.

The written scope names the exact expected behavior and deliverables. Your developer reviews and approves the patch before any merge or deployment. We do not merge into your repository or deploy to production as part of this pilot.

From inquiry to handover

  1. Free fit check. Describe expected and actual behavior, a safe way to reproduce the issue, and who can review a patch. We confirm whether the $99 pilot fits.
  2. Agree the work. Confirm one defect, review responsibilities, checks, timing, and price before accepting paid work. The existing corrections guarantee applies to the agreed deliverables. Additional troubleshooting and ongoing maintenance are outside this pilot unless separately agreed.
  3. Review the result. Review the proposed change, test evidence, and explanation. After approval and confirmed payment, receive the final patch and agreed handover materials. Your team controls release.

Outside this pilot

Emergency production incidents; authentication, authorization, or security vulnerabilities; payment processing; sensitive personal or customer data; database migrations; and broad rewrites or new features. No production credentials or privileged system access are needed for the fit inquiry.

Public work you can inspect

Grafana pull request #131070 documents a short-URL compatibility change and regression tests. Grafana maintainers merged it on September 25, 2026. The public discussion shows the proposed behavior, checks, and review. This is an open-source contribution, not paid client work or an endorsement of this service.