From 8 hours of weekly data entry to zero.
What life felt like
The organization ran a job placement program that required external users, employers, to submit detailed job requests through a public-facing form. Staff would receive email notifications, then manually re-enter each submission into Salesforce. With dozens of requests per week, this consumed nearly two full working days per month.
Program leads were stuck between mission work and data entry. The CRM was "accurate" only after someone had copied fields by hand, a fragile step that didn't scale.
What they were trying to avoid
Nobody wanted another expensive product layer or a multi-year integration roadmap for what was fundamentally a handoff problem. The fear wasn't Salesforce, it was scope creep and another system to babysit. The bar was: fix the broken handoff without making employers jump through a new portal maze.
What was really wrong, and what I built
The real problem wasn't "bad Salesforce", it was that submissions never landed in Salesforce as structured records. Re-entry was the symptom. The fix was to preserve the employer-facing experience while piping data straight into the org.
I designed and built a FormAssembly form that matched the existing field set, preserving familiarity, with a connector that created records on a custom object in Salesforce. A Flow on create routed work by territory, sent employer confirmations, and created follow-up tasks for coordinators.
Integration architecture
How they run it now
Within two weeks of launch, manual data entry dropped to zero. Staff who had spent hours re-entering submissions were redirected to direct program work. The error rate in new job request records fell to near zero, and the average time from submission to staff action dropped from two days to under an hour.
Twelve months post-implementation, the system continues to run without intervention and has processed over 400 job requests. The team adjusts small Flow parameters and email templates in-house, the engagement didn't require a standing retainer to "keep the pipes open."
Tools & technologies
Facing a similar handoff problem?
Let's talk about what's possible, including simpler paths than another platform.