Skip to content

For web agencies

From proposal to launch, and the support after it.

A website is a project with milestones, revisions and a launch, followed by months of support. Trelyn connects the accepted proposal, the build, the client's feedback on the actual site and the support cycle that follows, on one client record.

Sound familiar?

Where the work gets stuck.

  • The handover loses the scope

    What sales promised lives in a proposal PDF the developers never open.

  • Feedback by screenshot

    The client emails screenshots of the staging site; the team guesses which element they mean.

  • Launch week chaos

    Who is waiting on whom, content from the client, a DNS change, a final approval?

  • Support work is invisible

    After launch, small requests pile up untracked and unbilled.

The Trelyn workflow

One client, from build to support

A project for the build, a cycle for the support, both under the client's engagement.

  1. 01

    Proposal to project

    The accepted proposal wins the deal; the engagement and project start with the scope attached.

  2. 02

    Milestones and tasks

    Design, build, content and launch as milestones, with tasks that can be marked blocked by another task, with a reason.

  3. 03

    Review the real thing

    Designs as PDFs or images with pinned comments; the staging site reviewed by clicking elements on the page.

  4. 04

    Launch, then support

    After go-live, support runs as a recurring cycle; client requests arrive in the portal.

An example lifecycle

One client, start to finish.

Each step is a record in Trelyn, linked to the one before it.

  1. Lead
  2. ProposalAccepted online
  3. ProjectWebsite relaunch
  4. MilestonesDesign, build
  5. FilesAssets, content
  6. DeliverablesDesigns, staging
  7. RevisionsReview rounds
  8. Launch
  9. Support cycleMonthly