Angelo DoromalAutomation & Operations
Start a project
← Back to selected work

Selected work / 01 — Power Print

A print request. A clear next step.

I built Power Print’s quote-to-production setup in GoHighLevel. Here’s how one sample request moves from a form to the people, stages, and updates that follow.

Follow the story Let’s talk about your process
Project
Power Print
My part
Forms, CRM & automation
Inside
44 build & test screens
GoHighLevel implementation 04 chapters · 44 build screens Scroll to follow the request

01 The challenge

Someone still has to
pick up the request.

Five hundred flyers, glossy paper, next Friday. The form captures the ask. The next job is making sure those details reach the right place. I mapped this build around one question: who picks this up next?

The request
Capture what needs printing and how to reach the customer.
The details
Keep the print requirements with the contact and conversation.
The handoff
Give the job a stage and the team a next action.
The update
Let the customer know what’s happening with their order.

02 The build

Here’s where
the request goes.

I connected the form, contact record, pipeline, and workflows in GoHighLevel. Follow the four handoffs below to see what I configured at each one. The team still handles the quote, approval, and production decisions.

  1. Quote form
  2. Contact record
  3. Conversation
  4. Opportunity
  5. Pipeline stage
  6. Workflow
  7. Customer update
  8. Next action

Customer journey / pipeline

One order.
Every stage accounted for.

I set up seven stages for the route from a new request to a completed order. If a quote doesn’t go ahead, a separate closed / lost path stops the follow-up.

  1. 01
    New Quote RequestCustomer submits quote form
  2. 02
    ContactedTeam confirms details and ownership
  3. 03
    Quote sentCustomer receives the estimate
  4. 04
    Quote approvedProduction handoff is created
  5. 05
    In productionCustomer receives a progress update
  6. 06
    Ready for pickup / deliveryCustomer receives the next-step notice
  7. 07
    CompletedThank-you and review request are sent

03 The proof

The actual build,
open to inspection.

These are the 44 screens from the build: forms, sample records, messages, and workflow logs. Open a section, then select any image for a closer look.

My role

What I set up.

I configured the quote form, organised the contact fields, defined the pipeline stages, and built the workflows. The sample submissions, messages, and execution logs show how the setup was tested.

What I would improve next

What I’d tidy up before launch.

  • Replace the form’s placeholder consent text with the business-specific copy.
  • Confirm contact ownership rules; the sample record is unassigned.
  • Review duplicate project fields visible in the contact record.
  • Test each stage change and exit condition with the team, then measure live outcomes.

04 The result

A request with
a place to go next.

The build gives each request a contact record, a pipeline stage, and a set of follow-up actions. You can trace that setup through the sample records and workflow logs above.

For the customer

Know what happens next.

I configured messages for the request, quote follow-up, production, collection, and final thank-you.

For the team

Pick up with the details.

The contact record holds the request. The pipeline shows its stage. Internal tasks mark the next handoff.

For the system

Close the loop.

Completed orders and lost quotes have their own paths, so the follow-up can end at the right point.

This case study documents the configuration and sample tests. Live business results haven’t been measured.

Your next project

Where does your work get stuck?

Tell me what happens after a new enquiry comes in. We can start there.

Start a project Back to selected work