Work
Five client builds. What each one does.
Four are websites with lead capture and a CRM behind them, shaped to how each business runs. One shows what a fully custom front end looks like. Here is what we built, how the parts connect and what each one does today.
What’s inside each build
- 01Mae’s Sweets with SoulWebsite · Order inquiry form · CRM · Order pipeline · Customer confirmation · Internal notifications
- 02Lee H. Moultrie & AssociatesWebsite · Recruiting, speaking and insurance intake · CRM · Recruiting pipeline · Automation · Marketing infrastructure
- 03A’KERA CollectiveWebsite · Opportunity flow · Lead capture · Booking · CRM · Marketing infrastructure
- 04ACF Charleston ChapterWebsite · Chapter and community presence · Membership and interest capture · CRM connection
- 05Trae ModelsCustom visual design · Custom-built front end
Project 01 of 05
Mae’s Sweets with Soul
An order inquiry that goes somewhere.
Front door
- Website
Capture
- Order inquiry form
Hub
- CRM
Runs from the CRM
- Order pipeline
- Customer confirmation
- Internal notifications
- Problem
- Order requests need a clear way in, a place to be tracked and a prompt acknowledgement. Without them, they live in an inbox.
- What we built
- A website with an order inquiry form that feeds the CRM. Each inquiry enters an order pipeline, the customer gets a confirmation, and the team is notified internally.
- Current capability
- An order inquiry from the website creates a CRM record, enters the order pipeline, sends the customer a confirmation and notifies the team.
Project 02 of 05
Lee H. Moultrie & Associates
One website. Three intake paths. One CRM.
- Problem
- People asking about recruiting, speaking and insurance want different things. One generic contact form would send all three to the same place.
- What we built
- A website with separate intake paths for recruiting, speaking and insurance, all connected to one CRM. Recruiting has its own pipeline, with automation and marketing infrastructure behind it.
Front door
- Website
Three intake paths
- Recruiting intake
- Speaking intake
- Insurance intake
One CRM
- CRM
Behind the CRM
- Recruiting pipeline
- Automation
- Marketing infrastructure
- Current capability
- Recruiting, speaking and insurance inquiries each enter through their own path and land in the same CRM. Recruiting inquiries move through a recruiting pipeline.
- 01Website
- 02Opportunity flow
- 03Lead captureForms
- 04Booking
- 05CRM
Underneath it allMarketing infrastructure
Project 03 of 05
A’KERA Collective
An opportunity flow that ends in a booking.
- Problem
- People who want in on an opportunity need to see it, raise a hand and book a next step. If capture and booking aren’t connected, that interest has nowhere to go.
- What we built
- A website with an opportunity and career flow, forms for lead capture and a booking path, all connected to the CRM, with marketing infrastructure behind it.
- Current capability
- A visitor can move from the opportunity flow to a form and a booking, and the lead lands in the CRM.
Project 04 of 05
ACF Charleston Chapter
A chapter’s front door, connected to a CRM.
On the website
- Chapter information
- Business and community presence
Capture
- Membership and interest capture
Connected to
- CRM
- Problem
- A chapter needs to be easy to find and explain what it does. It also needs to give interested people and local businesses a way to get involved, with a record of who raised a hand.
- What we built
- A chapter website covering chapter information and business and community presence, with membership and interest capture connected to the CRM.
- Current capability
- Membership and interest submissions from the website connect to the CRM.
Project 05 of 05
Trae Models
A front door designed from scratch.
Design
- Custom visual design
Build
- Custom-built front end
- Problem
- A personal brand that depends on how it looks can’t sit on a template that looks like everyone else’s.
- What we built
- A fully custom visual design and front end, built from scratch instead of from a template.
- Why it’s here
- It shows the design side of a Website + System build: when the front door has to look premium, we design it for that.
The common thread
Different businesses. The same backbone.
Every build starts with a website people can act on, a way to capture who they are, and a CRM that holds it all. What happens after the CRM is where each business differs.
- WebsitePeople can act on it.
- Lead captureWho they are, what they asked.
- CRMIt all has somewhere to go.
- Built to fitPipelines, confirmations, booking and automation, shaped to the business.
See what a system around your business looks like.
The audit shows where leads are getting lost, what should be connected, and what to fix first.