Proof of Execution
Every build below started with one 30-minute call.
Twenty-seven years of agency history sat in a legacy Salesforce org held together by one shared login, and the business needed to move onto a supported edition without losing a record of how it had worked.
A documented and client-approved migration plan, a permanent full export locked as the recovery baseline, an import sequence with validation gates written into a build document, then a stabilization sprint that root-caused an encoding failure and a stale source export instead of patching symptoms
Five users on a supported edition at exactly five licenses with nothing over-purchased, calendars visible from every login, opportunities saveable, and every reconciliation closed against a named count.
"The client reported 73 missing records. The diff found roughly 1,100, because the real problem was not the 73, it was the two-week-old export the migration had been built from."
"A great communicator, which went a long way with making us feel super confident everything was getting done. When any kind of bumps arose she had speedy responses and very helpful explanations about how to troubleshoot."
Verified client review · Creative & Media Agency · Jun – Aug 2026
A device sales team was forecasting off a pipeline where 163 of 177 open deals had not moved in over a year, some of them for seven, and 105 of them still belonged to a sales rep who had left without being mentioned at kickoff.
A data assessment delivered the morning of the first working session, then a distributor-aware parent and child entity model, four purpose-built pipelines with full stage sets, a gated 12-stage sales pipeline with probability weighting where unqualified deals sit at zero percent, and a 100-point hospital tier-scoring model held back from launch until it was QA'd against known-answer records
Leadership reads a demand matrix instead of guessing, and the forecast cannot overstate itself because the pipeline documentation states which stages count as procurement-grade until two quarters of real conversion data exist.
"The original specification called for a custom object. The client's plan tier does not include custom objects. We found that out before building it, and shipped the version their tier supports instead of an upgrade invoice."
"Her communication was always clear, she understood exactly what was needed, and she consistently delivered thoughtful, high-quality work on time. She took feedback exceptionally well and was proactive in finding solutions whenever questions arose."
Verified client review · Medical Device Manufacturer · Jun – Aug 2026
A dredging company with deep operational craft had no CRM, no coordinated way to reach the waterfront residents who fund a project together, and books still structured the way a bankruptcy had left them.
A CRM and phone stack stood up and operated day to day, plus a repeatable cluster-mobilization playbook: a verified contact list, a five-email sequence sent from the client's own accounts, call-priority lists ordered by open and click behavior, a certificate of insurance issued to the property owners' association, and a daily-report template delivered from the job site
One mobilization coordinated from a single system, and a playbook the team runs on the next four communities without rebuilding it.
"The client did not buy a retainer pitch. He watched the system run for six weeks and picked the number himself."
A membership business run by attorneys needed revenue infrastructure that would survive bar-rule scrutiny, which meant every growth mechanism had to be built with the ethics constraint designed in rather than reviewed at the end.
Inline membership checkout wired end to end and tested on a real card through to refund, an outbound engine with mailbox warm-up on a written schedule and numeric escalation thresholds for bounces and spam complaints, a compliance memo routed to outside ethics counsel in two states with the affected programs paused while it sat, and documented attorney sign-off enforced on every creative
Growth mechanisms ship with the compliance question already answered, and the founders get an honest read on vendors and spend instead of a rubber stamp.
"Bar rules are not a legal review at the end. They are a system requirement at the start."
Client names are withheld. Industry, size, timeline, and metrics are drawn from engagement records.
What Buyers Ask Here
Are these engagements verified?
Every number on this page comes from work CWT Studio delivered, and the client identities stay private unless a client has agreed to be named. Metrics are stated as they were measured in the account.
What size company do you work with?
B2B companies between $2M and $20M in revenue, with work landing in medical device and biomedical, healthcare, legal, professional services, marine services, and B2B software.
Can records survive a migration this large?
Yes, with validation gates at each stage. The photo agency engagement moved 27 years of history and 238,945 records with zero loss, checked against source counts before cutover.
What happens after the 30-minute intro?
A paid written review of the current state, then a build sequenced by what costs the most while it stays broken. Each case study on this page followed that path.
Every one of these engagements started with a 30-minute call, and the build followed from what it found.