Start here

Agency quick-start

Go from a scoped milestone to a client-ready proof packet in one focused session.

Agency owners and project leads8 min readUpdated July 28, 2026
Download a Markdown copy
Before you begin

Choose one small, reviewable milestone

For your first Greenlit project, use a milestone that is already described in a signed or agreed scope and has a staging build ready for review.

The best first milestone has three to six outcomes that a client can understand. Avoid using an entire website launch as one milestone.

  • Use a public HTTPS staging URL that your agency controls.
  • Use a redacted, synthetic, or expressly non-confidential SOW section unless the analysis screen confirms a paid data mode.
  • Choose one client decision-maker and agree on a review deadline.
  • Keep contracts, formal signatures, accounting records, and payments in their existing systems.
Public walkthrough path

Explore the complete proof flow

  1. 01
    Open the walkthrough

    Launch the guided synthetic demo. It requires no account and demonstrates the complete workflow; account-backed project imports are not currently offered through the public site.

  2. 02
    Inspect the promise

    Start with the included synthetic SOW and see how exact source language stays attached to the milestone.

  3. 03
    Review every criterion

    Check each exact source quote and confirm the grounded outcomes that define what done means.

  4. 04
    Preview staging ownership

    See where an agency proves control of a public HTTPS staging origin before a retained verification run.

  5. 05
    Inspect the checks

    Review the supported typed checks and compare expected outcomes with the evidence captured from the sample build.

  6. 06
    Follow the failure and fix

    See Greenlit catch a hidden HTTP failure, then rerun the same frozen criteria against the corrected build.

  7. 07
    Prepare client review

    Preview the named-reviewer handoff, milestone value, evidence summary, and invoice disclosure.

  8. 08
    Understand secure sharing

    See how a recipient-bound review link and separate access code protect the client decision path.

  9. 09
    Record the decision

    Use the sample client view to approve or request changes and see how new scope stays separate from corrections.

  10. 10
    Finish the handoff

    Open the sample approval record and inspect the evidence, decision, and invoice-ready status that an agency would retain.

What the walkthrough demonstrates

  • An agency can trace every criterion to exact agreed source language.
  • A browser check can expose a failure hidden behind a successful-looking page.
  • The same frozen promise can be rerun after the build is corrected.
  • A client can make a clear approve or request-changes decision.
  • The resulting record can connect evidence, the client decision, and invoice readiness.