Skip to content
Sean Marroquin
Esc
  • HomePage
  • WorkPage
  • AboutPage
  • Start a projectPage
  • How this site is builtPage
  • BlogPage
  • DownloadsPage
  • Client PortalClients
  • TerraLoopCase study
  • ListoCase study
  • The Listening RoomCase study
  • PasslineCase study
  • AccuBetsCase study
  • How this site is builtPost
  • Why every client gets a portalPost
  • Switch between light and darkAction
  • Copy my email addressAction
  • PWNTT ArcadePlay
  • Play The Deploy TrailPlay
  • Play Merge ConflictPlay

Use the arrow keys to move and Enter to open.

All posts

Why every client gets a portal

1 min read

When you hire a developer, three questions come up again and again: where are we, what will this cost, and what happens next. If the answers live in someone's inbox, you have to ask. If they live in a portal, you can look.

Change requests with a price attached

Scope creep is rarely anyone's fault. A request sounds small, the work turns out to be large, and the invoice becomes the first time anyone talks about cost.

So every request follows the same path:

  1. You submit it in the portal, in your own words.
  2. I review it and reply with a quote, or mark it as covered by our agreement.
  3. You approve or decline.
  4. Only then does work start.

The quote comes before the work, every time. You can try the flow on the home page, which runs the same rules as the real thing.

One place for the paperwork

Invoices, files, and forms sit next to the project they belong to. When you need last month's invoice or the final logo files, they are where you left them.

Fewer meetings

Milestones update as work lands. If you want to know whether the booking page is done, the answer is on your dashboard. Calls are for decisions, not status.