A workflow your team still runs by hand, or a research platform that has to hold up through a pilot. We’ll tell you what we’d build first, where a model belongs, and where a human check stays.
Your team’s manual work, done by software
Smplfy is an engineering team outside Boston, building for finance shops, law firms, research groups and agencies. We put AI to work inside your operations, connect the tools you already run, and stay on to keep it all working.
Work we’ve shipped for

















A manual-heavy process, start to finish
- Work comes in from email, forms and other systemsSystemCaptured once, in one place.
- The routine steps run on their ownSystemSorting, data entry, document handling and handoffs.
- Your team handles the exceptionsYour teamPeople decide the cases that need judgment.
- Every system shows the same numbersSystemYour CRM, finance and other tools update together.
- It keeps runningSmplfyWe stay on to maintain and extend it.
Who we build for
Each page shows the workflow we take on, the work we’ve done, and how an engagement starts.
Where we’ve done it
Five of the 16 case studies on the site. Our longest-running client has been with us since 2021.
nCred
A client portal with Salesforce-connected dashboards and self-serve document uploads for a credentialing company.
Read the case studySamson Funding
An internal loan platform covering intake, document review, due-diligence integrations and payout calculations.
Read the case studyFundz
Gmail, HubSpot and Salesforce connectors that put market signals inside the CRM.
Read the case studyA Georgia Tech research group
Two AI learning platforms run by one engineering team.
Read the case studyA solar services company
Estimates, approvals, quotes and contracts moved into one HubSpot workflow.
Read the case studyWhat clients say
“If you need an expert software engineer that can do the work of many, then he’s your guy. Also, if you need help planning or architecting the project, he is an expert in this too.”
“Charlie has a unique and creative approach to code, he finds a way to get things done even when they seem impossible. He has insane communication skills and work ethic.”
“Charlie is technically impeccable and always meets our deadlines. Charlie made helpful suggestions and was gracious enough to help me when I had emergencies.”
“Absolute rockstar, if you have any dev needs he is the guy to talk to.”
What we build
Most projects mix all three. A typical two-system integration is live in two to four weeks.
Manual work that runs on its own
Intake, data entry, document handling and handoffs your team does by hand today, rebuilt as workflows that run without them. A person checks only the exceptions.
Systems that agree
Your CRM, practice tools and finance stack stop disagreeing. We build the integrations and the system of record so one number is true everywhere.
AI that a person still checks
We connect OpenAI, Claude and Gemini to your CRM and other systems. A person reviews the exceptions, and we monitor the results so they stay accurate.
How we work
You see a written scope before you commit to anything.
One call, one written scope
We map the systems involved, say where AI actually earns its place, and name the risks.
A fixed-scope first project
One integration, one document-AI intake pipeline, one dashboard, one automation cleanup. The entry point, not the relationship.
An ongoing engineering retainer
A small dedicated team that owns the platform, ships weekly, and absorbs integration, model updates and maintenance work. Most clients convert and stay for years.
We also build the software behind funded research
We are also the engineering team on federally funded research software, from prototype to production: a K–8 mathematics platform backed by $1M in federal SBIR funding, a 30-day pilot MVP deployed to multiple school districts, and an NSF CAREER-funded education study platform.
That work includes FERPA-compliant logging, reporting built for principal investigators, and disclosure packages that clear district IT review.
See how we work with research teams
Charlie Media LLC (dba Smplfy) is an SDO-certified MBE.
Questions we get before a first call
What if the first project doesn’t work out?
The first project has a fixed scope, and you read that scope in writing before you commit to anything. A retainer only starts if you choose one afterwards.
Who does the work?
Charlie scopes every project and makes the architecture calls. Smplfy’s own engineers build it, and Charlie stays your single point of accountability.
How long does an integration take?
Two to four weeks from kickoff to cutover when both systems have documented APIs and access comes quickly. Slow access approvals or messy records can stretch that to six to eight.
Full answerWhat does a retainer include?
A reserved block of engineering hours each month, with a written plan for how they are spent, from engineers who already know your systems. Not a ticket queue.
Full answerFreelancer, agency or senior engineer?
A freelancer suits a simple one-way sync. An agency makes sense when the integration is one part of a larger platform build. Most two-system work fits a senior engineer best.
Full answerWhen is automating not worth it?
When it saves less than about five hours a month, changes every few weeks, or needs a judgement call in more than one case in five.
Full answerSmplfy is led by Charlie Meng, founder and architect, PhD from Northeastern, formerly a senior software engineer at HubSpot and MathWorks, Top Rated Plus on Upwork. Charlie scopes every engagement, makes the architecture calls, and stays accountable for the result; the Smplfy team carries delivery.
About Smplfy and our terms.
Tell us what you’re building
Charlie reads every message and replies himself. Prefer to talk? Book a call with Charlie, or email contact@smplfy.co. What you send is used only to reply to you.