CASE STUDY / SAAS / CRM / BOOKING
A placement workflow that keeps bookings, documents, and status in sync.
ACE turns clinical placement coordination into a connected workflow — from location search and booking to CRM updates, milestone documents, and coordinator visibility.
FULL-STACK DEVELOPER · OCT 2025 – JAN 2026 · CONTRACT
PLACEMENT #1048
SIMULATED
- STUDENT
- STU-104
- LOCATION
- CLINIC 04
- STATUS
- DOCS READY
- NEXT
- CONFIRMATION
BOOKING FLOW
Search → booking → CRM
DOCUMENT FLOW
Milestone → document → completion
INTEGRATIONS
CRM · PandaDoc · Maps · Auth
DELIVERY
Architecture → development → QA
THE PROBLEM
Before ACE, the workflow was fragmented.
Placement coordinators had to keep bookings, student profiles, document packs, CRM records, and communication status aligned across separate tools. Watch the system connect.
THE WORKFLOW
One placement. Every event accounted for.
Click any event to see what happens at that point in the workflow.
SEARCH
- Location search
- Map-based discovery
- Placement availability
THE SYSTEM
One application. Multiple systems. One workflow.
The placement is the source of truth — every layer reads from it and keeps its own systems aligned.
EXPERIENCE
Next.js · TypeScript · Tailwind · Clerk
APPLICATION
Laravel API
INTEGRATIONS
External services
OPERATIONS
Delivery discipline
INTEGRATIONS
The integrations are part of the product.
Hover a system to see what ACE uses it for.
ACE
ENGINEERING DECISIONS
Why the system stays synchronized.
Scheduling, profiles, and documents stay consistent across the web app and the CRM because everything moves through one API.
IN PRACTICE
A coordinator's morning, simulated.
One placement moving through the connected workflow — no tool-hopping, no re-entry.
A COORDINATOR'S MORNING — SIMULATED
press play to simulate one placement
WHAT SHIPPED
From placement search to completion.
- Location search and placement discovery
- Booking workflow
- CRM synchronization
- Placement milestone handling
- Automated document workflows
- Coordinator status visibility
- Third-party integrations
- QA and deployment
MY ROLE: Architecture · Full-stack development · Integrations · Deployment · QA
TECHNOLOGY
System inventory.
ace / stack
FRONTEND
- Next.js
- TypeScript
- Tailwind
- Clerk
BACKEND
- Laravel
- API
- Scheduling
- Permissions
INTEGRATIONS
- Pipedrive
- PandaDoc
- Mapbox
DELIVERY
- Vercel
- QA
- Deployment
Still moving business data between tools?
I build systems that connect the workflow instead of adding another tool for your team to manage.