Profitto Agency← Operating debrief

The working record · Kannan Chotai

Process & evidence

Original work, tests, and conversations behind the debrief.

I coordinated client delivery and a two-person team while configuring the systems between advertising and appointments. These records show the creative work, the configuration, and what happened when the information did not arrive as intended.

Original records from the agency’s client engagements. Private details are redacted; select an image to inspect it at full size.

01 / The journey

An offer became
a delivery process.

  1. July 2025 · Beginning

    Develop the offer and acquire clients.

    I started Profitto to help epoxy-flooring contractors turn inquiries into sales appointments. Client acquisition brought responsibility for the work that followed.

  2. During operations · Team and systems

    Coordinate two connected kinds of work.

    I managed a media buyer and a creative director, coordinated client requirements and brand assets, and configured the appointment process. The team’s advertising work had to connect with lead capture, qualification, booking, and follow-up.

  3. September–October 2025 · Testing records

    Investigate the handoff to the client.

    Test notifications and the support exchange document a gap between a completed booking and complete information. I checked results, shared what was failing, and requested the fields the client needed.

  4. October–November 2025 · Delivery records

    Work across client engagements.

    A completed agreement, script variants, a finished client video, and a successful payment record document different parts of the agency’s work.

  5. December 2025 · Closure

    Recognize the limits of the business.

    Client engagements ended and Profitto became inactive. Solving individual delivery problems did not make the business sustainable.

02 / Creative production

Script options → finished client ad

The source script separates three residential hooks: a discount, a homeowner’s problem, and the desired result. The featured video uses the discount opening and follows it with the service description and consultation offer.

Client promotional video, approximately 41 seconds, featuring the discount opening and consultation offer.

One service, three openings.

Original residential script showing discount, pain, and lifestyle hooks.
Original October 17 script with three residential hooks: discount, pain, and lifestyle. All three variants ran as ads.

My contribution: coordinating client requirements, brand assets, and creative delivery with the team. The creative director handled ad production.

Read the source script for this version

Residential H1: Hey Wisconsin homeowners, for a limited time you can save 20% on premium epoxy garage and basement flooring that delivers a sleek, showroom-style finish built to last through harsh Midwest winters.

Residential B1: At Custom Epoxy Solutions, we specialize in premium epoxy floors designed for Wisconsin homes. Our craftsmanship and industrial-grade coatings deliver flawless finishes that resist cracks, stains, and hot-tire pickup, while adding long-term beauty and value to your property. Right now, for a limited time, you can save 20% when you upgrade your garage or basement floor. Click Learn More to schedule your free consultation.

Residential H1 and B1 from the client campaign script.

03 / Configuration and handoffs

Make the next step explicit.

The retained Appointwise setup shows the questions, qualification rules, and branches I configured. The work used existing software: the platform provided the AI and builder; my responsibility was how the client’s process fit together.

The conversation path

Appointwise conversation builder showing opener, right-person check, project type, budget, qualification, booking, objection handling, and disqualification branches.
The retained Appointwise conversation workflow, captured in September 2026: qualification, booking, objection handling, and follow-up paths.

The information required before booking

Appointwise agent instructions and criteria requiring homeowner or decision-maker status, a service-area match, and a full street address and ZIP code before booking.
The agent’s booking criteria require a street address and ZIP code, along with homeowner or decision-maker status and a service-area match.

The CRM notification template

GoHighLevel workflow screenshot with an internal-notification step and placeholders for contact details, address, appointment start time, and qualification answers.
GoHighLevel’s internal-notification step, preserved in the support exchange, with fields for contact information, address, appointment time, and qualification answers.
See the lead-form brief and a sample qualification conversation
Original lead-form questions covering homeownership, timing, and contact-field labels.
The working brief specifies the homeownership, project-timing, and contact fields to collect.
Original instructions asking the builder to align the form wording, tone, visuals, and ad copy.
The same brief includes production instructions for the form and creative handoff.
Example conversation asks about project type, surface condition, scheduling, and the address needed to lock in an appointment.
An example conversation progressing from project questions to scheduling and address collection.

04 / Testing and troubleshooting

The booking and the notification
could disagree.

I needed the client’s notification to contain the information collected during qualification and booking. The screenshots show why a successful booking alone was an incomplete test.

Test example A / Address missing

The conversation has it. The notification doesn’t.

Redacted test conversation confirms an address, but the resulting appointment notification shows undefined where the address should be. The appointment time is populated.
The test conversation includes an address, covered here for privacy. The notification beneath it displays “undefined” while retaining the appointment time and qualification answers.
Test example B / Different fields missing

Another output was only partly complete.

Redacted appointment notification with an address and ZIP code populated, a visible appointment date and time, and blank email and lower qualification fields.
In this separate example, the address, ZIP code, and time are populated; the email and lower qualification fields appear blank. Values under black bars were present in the original.

Working through it with support

I tried custom workflows and checked the CRM side, then kept testing with platform support over roughly a week. The preserved WhatsApp messages show my observations, a proposed workaround, and the request to test again.

01 / Report what failed
WhatsApp exchange reporting successful calendar bookings but missing address and postal code, including a recurrence after tests had worked.
I distinguished the successful booking from the missing information and reported that the issue persisted despite earlier successful tests.
02 / Refine the proposed change
Support proposes sending a conversation summary including the address; I agree and ask to include the Facebook form fields.
On October 2, support proposes a summary containing the address. I agree and ask to include the Facebook form fields too.
Support asks me to test and report how it goes.
A further message asks me to test the result and report back.

Outcome and lesson

Working with platform support, I resolved the notification issue and verified that the required information populated correctly. The messages show the testing, feedback, and persistence that went into getting it working.

I learned to verify the complete path from an answer to the client’s output—and to repeat a test after an apparent success. On a future project, I would keep a dated input–expected output–actual output record for every change.

05 / Client engagement

Commercial work, documented.

A completed service agreement and a successful Stripe payment document the agency’s client work.

A successful payment recorded in Stripe

This client payment is marked Succeeded, dated November 2, 2025. The original amount, customer information, payment details, and transaction identifier are covered.

A selected Stripe payment row with Succeeded status and November 2, 2025 date visible. Amount, payment details, identifier, and customer information are blacked out.
Original Stripe payment record with sensitive details permanently redacted.
View the completed-agreement record

The service agreement’s signature audit records completion on October 17, 2025. The excerpts below come from three separate regions of the same audit page. Client identity, signatures, financial terms, and identifiers are omitted.

Original title: Profitto Agency Contract Service Agreement.
Original signature-audit status: Signed.
Original audit entry: October 17, 2025, 00:31:06 UTC. The document has been completed.
View the Appointwise platform record

Appointwise Business plan invoice, issued September 25, 2025, covering September 25–October 25. Two excerpts from the original invoice.

Original Appointwise invoice issue date September 25, 2025.
Original invoice description Business, September 25 to October 25, 2025.
06 / What I take forward

Responsibility continued
after the sale.

I had to coordinate the team’s work, communicate with clients, and stay involved when the system’s output was incomplete. Delegation made delivery possible; it did not remove my responsibility for connecting the pieces.

Profitto became inactive in December 2025. The work left me with practical questions about data flow, program logic, and reliability—and a reason to study the software beneath the interfaces more deeply.

Return to the operating debrief →