SoftGirlOps Operations consultancy

Backend Glow-Up · Proposal

J. McAllister Events Backend

A 90-day Backend Glow-Up designed to create visibility, accountability, and consistency behind every event.

Prepared exclusively for Jahlil McAllisterCreated June 2026

Prepared for

Jahlil McAllister

Prepared by

SoftGirlOps

Prototype

View link →

01What I heard

What I heard

Jahlil, thank you again for such an honest conversation.

What stood out most is that J. McAllister Events already delivers a beautiful, high-touch, custom client experience. The issue is not the quality of the work.

The issue is that too much of the backend still depends on you remembering, reminding, checking, correcting, and carrying the details.

You shared that tasks often live in your head, your team needs daily direction to know what happens next, SOPs exist but are not always followed, and clients sometimes ask “what’s next?” because the process is not visible enough. You also shared that stepping away is difficult because the business still depends on you watching the moving pieces.

The goal of this build is not to make J. McAllister Events less personal.

The goal is to create a backend that protects the personal, luxury experience your clients already receive.

02The opportunity

Every event should be customized. The backend should not have to be.

Right now, each event has unique details, timelines, vendors, client preferences, payments, team responsibilities, and follow-ups. Without one central source of truth, those details depend too heavily on memory and manual oversight.

This Backend Glow-Up is designed to move the business from:

From

“Jahlil has to know and remind everyone.”

To

“The system shows the team what needs to happen next.”

03The build

J. McAllister Events Backend

A custom backend designed specifically around how J. McAllister Events operates. This build will create one centralized place for:

  • Active events
  • Event stages
  • Team responsibilities
  • Overdue tasks
  • Client details
  • Vendor information
  • Payment visibility
  • Custom event requirements
  • Client communication
  • Post-event follow-up
04What’s included

What’s included

Client journey mapping

We will map the current JMC client journey from inquiry through post-event follow-up, including consultation, preliminary numbers, contract and retainer, concept deck, mood board, proposal, renders, event week, event day, and post-event closeout.

Backend dashboard

A central dashboard that shows:

  • Active events
  • Current event stage
  • What is due
  • What is overdue
  • Who owns each task
  • What needs Jahlil’s attention
  • What is coming up next

Event management system

Each event will have a dedicated workspace for:

  • Client information
  • Event date and type
  • Vendor details
  • Payment tracking
  • Files and assets
  • Brand colors
  • ADA needs
  • Venue notes
  • Special requests
  • Internal team notes
  • Custom event exceptions

Team visibility & accountability

Custom views for Jahlil, Becky, Raven, and future team members so each person can clearly see what they own, what is due, what is overdue, and what needs to be escalated.

This is designed to reduce the need for constant daily check-ins and verbal reminders.

Built-in support agents

The backend will also include three support layers designed to reduce manual oversight.

Auditor

Flags overdue items, missing information, slipped follow-ups, events sitting too long in one stage, and post-event opportunities that have not been triggered.

Operator

Surfaces what needs attention across events, payments, deadlines, and team responsibilities.

Concierge

Supports repeat client questions and next-step visibility where appropriate, with clear escalation back to the team when a human response is needed.

Client communication system

Creation of branded client communication templates using J. McAllister Events’ existing brand direction, colors, voice, and visual style. This may include:

  • Inquiry follow-up
  • Booking confirmation
  • Next-step updates
  • Proposal reminders
  • Event-week communication
  • Thank-you messages
  • Testimonial requests
  • Referral requests

Returning client workflow

A streamlined manual-add process for long-term or returning clients who may bypass traditional forms, while still ensuring their event is tracked inside the backend.

Post-event experience

A structured closeout process so the relationship does not simply end after event day. This includes:

  • Thank-you communication
  • Gallery delivery workflow
  • Testimonial request
  • Referral request
  • Future rebooking opportunity

Team training & handoff

Training and walkthroughs so the team understands how to use the backend, follow the process, and maintain the system after launch.

0590-day timeline

90-day timeline

Phase one

Discovery & blueprint

Review current operations, document workflows, confirm roles, and map the backend structure.

Phase two

Backend build

Build the dashboard, event workspaces, team views, event stages, task structure, and visibility system.

Phase three

Communication & automation

Create client communication templates, reminders, notifications, and workflow automations.

Phase four

Testing & training

Test the system with sample events, refine the workflow, and train the team.

Phase five

Launch & handoff

Final walkthrough, optimization, and transition into active use.

06What this is not

What this is not

This is not a generic template, a simple Dubsado clean-up, or a set of disconnected automations.

This is a custom backend operating system designed around how J. McAllister Events actually runs.

This does not include:

  • Full website redesign
  • Public-facing website development
  • Ongoing daily admin support
  • Managing JMC clients or vendors on behalf of the team
  • Replacing the internal graphic designer
  • Rebuilding unrelated SOPs outside of the backend workflow
07Visual prototype

See it in motion

To help bring the vision to life, I created a clickable prototype that demonstrates how the backend could function.

The prototype shows how visibility, accountability, communication, and event management can come together inside the J. McAllister Events Backend.

View the prototype

jmc-backend-demo.softgirlops.com

08Expected outcomes

Expected outcomes

Upon completion, the Backend Glow-Up is designed to help J. McAllister Events create:

Fewer daily check-in calls

The team can see what needs to happen without needing constant verbal direction from Jahlil.

Clearer team ownership

Becky, Raven, and future team members can see what they own, what is due, what is overdue, and what needs to be escalated.

Better event visibility

Jahlil can quickly see where every active event stands, what is waiting, what is urgent, and what may slip.

A cleaner client experience

Clients receive clearer next steps, updates, expectations, and post-event follow-up.

A more consistent post-event loop

Testimonials, gallery delivery, referral asks, and future opportunities are no longer left to memory.

More space for leadership

The business becomes less dependent on Jahlil being the memory, manager, and emergency backup for every moving piece.

09Investment

$9,000

Backend Glow-Up for J. McAllister Events

Pay in full$9,000
Two payments$4,500 to start, and $4,500 at day 45.
Three payments$3,000 to start, $3,000 at day 30, and $3,000 at day 60.

Project start date is reserved upon signed agreement and initial payment.

10Next steps

Next steps

  1. Review the proposal and prototype.
  2. Bring any questions to our follow-up conversation.
  3. Confirm the payment option that feels most workable.
  4. Sign the agreement and complete the initial payment.
  5. Begin Discovery & Blueprint.

Thank you for the opportunity to learn more about J. McAllister Events. I’m excited about the possibility of helping you create a backend that supports the level of excellence your clients already experience.

Sabrina Amai
SoftGirlOps