Mendix project rescueGet a stalled Mendix project shipping again.
Five Stones started by taking over failed Mendix projects from offshore vendors. We review what's there, keep what works, fix what doesn't, and deliver what was promised.
Warning signs
Does this sound like your project?
If two or more of these are true, an outside review will pay for itself.
Releases keep slipping
Every sprint ends with "almost done", and the launch date has moved more than once.
Every fix breaks something
Small changes ripple through microflows nobody fully understands.
It gets slower every month
Pages and batch jobs that were fine in testing crawl with real data.
The team keeps changing
New faces every few months, and each one starts over learning your business.
Security is an afterthought
Entity access and roles were "to be done later", and later never came.
Nobody owns the architecture
The domain model grew page by page, and integrations are held together by hand.
How a rescue works
Review, plan, stabilize, deliver.
You'll know what you're dealing with before you commit to anything beyond the review.
- 01
Review
Senior engineers read the model, microflows, security, performance and integrations, and talk to the people who use the app.
- 02
Plan
You get a written assessment: what to keep, what to fix, what to rebuild, ranked by risk and cost, with the team it takes.
- 03
Stabilize
We fix the dangerous things first: security, data integrity, performance and the deployment pipeline.
- 04
Deliver
Then we ship the backlog in short, demoed releases, with the same named engineers throughout.
Why Five Stones
We've cleaned up more offshore Mendix code than we'd like to admit.
Enterprises choose Mendix for consistency, reuse, security and speed, then hand the build to a large offshore firm promising high performance at low cost. What arrives is high turnover and little experience in design, architecture or the business.
- U.S.-based senior engineers, named for the life of the project
- Work alongside your current vendor, or take over completely
- You own the code and the documentation
Questions
Rescue questions, answered.
How do I know if my Mendix project needs rescuing?
Common signs: releases keep slipping, every change breaks something else, performance gets worse as data grows, the team keeps turning over, and nobody can explain the domain model. If two or more sound familiar, an outside review is worth it.
Will you rewrite everything?
Rarely. Most Mendix projects can be saved. We keep what works, refactor what doesn't, and only rebuild modules when that is cheaper than fixing them. The review tells you which is which before you commit to anything.
Can you work alongside our current vendor?
Yes. Some clients bring us in quietly to review code and architecture while the existing team keeps working; others hand the project over completely. We'll recommend what fits.
What do we get from the review?
A written assessment of the domain model, microflows, security, performance and integrations, a list of the risks ranked by impact, and a plan to get the project shipping again, with the team it would take.
What happens after the project is stable?
The same engineers keep delivering new features and supporting the app, or hand it back to your team with documentation and training. Either way, you own the code.
Modesto, California
Is your Mendix project in trouble?
Tell us what's happening. An engineer will call you back, and the first conversation is free.