Consulting and development
Business systems that keep up with your business
One senior team for the systems your business runs on, with or without Salesforce. We build enterprise software, bring Salesforce into a landscape or introduce it for the first time, and make changes small and safe again when a setup has grown out of hand.
Problems we solve
Each of these has a technical cause. You don't need to know which one. Finding it is our job.
“Every Salesforce change takes too long, and something else breaks.”
- What we do
- We restructure a grown, tangled Salesforce setup into clearly separated building blocks, and remove what is no longer needed.
- What you get
- Changes become small, predictable and fast. New requirements stop being a risk.
“Releases are stressful. We find the bugs in production.”
- What we do
- We set up automated checks and a reliable release process, so problems are caught before they reach your users.
- What you get
- Calm, frequent releases instead of big, risky ones. Fewer incidents, fewer rollbacks.
“Salesforce and our other systems don't fit together.”
- What we do
- We connect Salesforce and the rest of your systems through events, so data flows reliably and in near real time.
- What you get
- One consistent picture across your systems. No manual reconciliation, no fragile one-off connections.
“We have grown, and our setup hasn't grown with us.”
- What we do
- We bring architecture, processes and governance up to the level your company has reached: clear responsibilities, auditability, security and stable operations.
- What you get
- A platform that passes the scrutiny of large customers, auditors and security reviews, and keeps up with your growth.
“We run two systems for the same thing.”
- What we do
- We plan and carry out the move from parallel systems to one platform, for example after an expansion or a merger, including the migration path and the alignment between the teams involved.
- What you get
- One system, lower cost, one way of working.
“We're considering Salesforce, and we don't want to get it wrong from the start.”
- What we do
- We help decide whether Salesforce fits, which parts of your business belong in it, and how it connects to what you already run. Then we introduce it in steps, with your people trained along the way.
- What you get
- A Salesforce that fits your business from day one, instead of a setup you have to untangle later.
“We need a system landscape built, and Salesforce may not be part of it.”
- What we do
- We design and build enterprise software without Salesforce too: backends, portals, internal tools and the connections between them, on a stack chosen for your case.
- What you get
- A landscape built for how your business works, not around one vendor.
“We need something built, and it doesn't fit neatly into Salesforce.”
- What we do
- We build custom software on Salesforce and outside it: backends, web applications, mobile apps and prototypes, connected to Salesforce through events.
- What you get
- The right solution in the right place, built by one team instead of several vendors.
“We need senior technical judgment, but not a full-time hire.”
- What we do
- We review architectures and vendor proposals, carry out technical due diligence, act as your part-time architect or CTO, and train your team.
- What you get
- Sound decisions before money is spent.
How we approach it
What becomes possible
Salesforce setups usually grow screen by screen, until everything depends on everything and every change is a risk. There are well-proven ways out of that, borrowed from how large software systems are built. Which of them fit you depends on your setup, your team and where you are going. These are the ones we reach for most often.
Change one area without breaking another
Sales, service, finance and fulfillment can each own their part of the setup, so a change in one of them stays in that one, and several teams can work at the same time.
How we get there
We draw the boundaries along your business areas, usually in a workshop with the people who know the processes, and untangle the setup along those lines, one area at a time.
Add systems without rebuilding the old ones
When something happens, an order placed, a contract signed, every part of your landscape that cares can react on its own. New systems and processes join without anyone touching the existing ones, and one system going down does not stop the rest.
How we get there
Instead of wiring systems directly to each other, each system announces what happened as a domain event, written in the words your business uses. Where it fits, on Salesforce itself; where volumes are high, on platforms built for it, such as Kafka.
Grow without hitting the ceiling
Salesforce is good at your customer processes and the people who run them. It is less good at high volumes, heavy processing and data that many systems share. When those live elsewhere, growth means adding capacity, not starting over.
How we get there
We help decide what belongs in Salesforce and what does not, and build the other side too: backends, web and mobile apps, connected through the same events.
Release often, without the stress
Small changes that go live every week, each checked automatically, with a way back if something goes wrong. Fewer incidents, no late nights before a release.
How we get there
A release process on the tools you already use, with automated checks in front of production. Your team runs it; we set it up and train them.
For the engineers on your team, the full reasoning is on our blog: Design Salesforce like a distributed system.
What we build
Enterprise software with Salesforce, around it or without it, from one team. The technologies are listed for the people on your team who will work with us.
Event-driven integration
Salesforce and your other systems, connected through events: reliable, in near real time, and without fragile one-off connections.
- Technologies
- Platform Events and the Pub/Sub API, Kafka and Redpanda, domain events, observability across systems.
Enterprise software
Backends, web applications, portals, internal tools and mobile apps, with Salesforce beside them or without it at all, and prototypes that test an idea before it is built. Connected through events, so each part can change on its own.
- Technologies
- Go, Java (Quarkus, Spring), PostgreSQL, React, Flutter.
Salesforce, introduced or untangled
A first Salesforce set up in clear business areas from the start, or a grown one untangled into them, each with automation that has one owner, so changes stay small and safe.
- Technologies
- Apex and platform development, the Trigger Actions framework, unlocked packages, dependency and impact analysis.
Calm, frequent releases
Automated checks and a repeatable release process, so problems are caught before they reach your users.
- Technologies
- CI/CD pipelines, test quality analysis, branching, environment and release strategy, developer tooling and AI-assisted workflows.
Architecture and advice
A target architecture, the consolidation of parallel systems, reviews and second opinions, and a part-time architect or CTO when you need one.
- Technologies
- Event Storming workshops, cross-system identity and data models, RFCs and decision records, technology evaluations, technical due diligence.
One team instead of two vendors
Most companies need two vendors, a Salesforce partner and a software engineering firm, and the problems live in the gap between them. We cover both in one senior team, and we are just as happy when the answer is no Salesforce at all.
Salesforce, and everything that is not Salesforce
Salesforce partners tend to solve every problem inside Salesforce. Software agencies treat Salesforce as a black box. We are at home on both sides, build either one, and say honestly what belongs in Salesforce, what does not, and whether you need it at all.
Deep platform knowledge
We know Salesforce from the inside, beyond certifications. We also build our own Salesforce developer tool, renmy runtime, and that takes knowing how the platform really behaves.
Results you can measure
We establish where you stand at the start and show the progress in numbers at the end. No slide decks based on gut feeling.
Senior people who have done it before
The people in the first conversation are the people who deliver: engineers and architects who have done this work inside large-scale platforms. No junior bench, no handover from sales to delivery.
Where to start
Two entry offers, one with a fixed price and one with a fixed scope. Larger engagements, such as an event-driven integration, a consolidation or custom software, usually follow from one of them.
Fixed price
Salesforce Health Check
Where the risks are, what slows your team down, and a prioritized plan to fix it.
€7,500 / $8,500, net
Fixed price for one production org. About two weeks from kickoff to walkthrough.
Provider: Renmy UG (haftungsbeschränkt) i.G.
About the Health CheckFixed scope
Release Process Sprint
A working, automated release process on your own project.
Usually two to four weeks.
The offer fixes the scope, the price and the end date before we start. Price and length depend on how many teams and environments are involved.
Provider: Renmy UG (haftungsbeschränkt) i.G.
About the SprintPrices net, plus VAT where it applies. For businesses only (§ 14 BGB).
How we work
First call
A conversation about what is slowing you down. Free and without obligation.
Written offer
Scope, price and timeline in writing, before any work starts.
The work
Done by the people you spoke to, with the access you give us and under an NDA.
Results
Where you started and where you are now, in numbers you can check.
Talk to us
Tell us what is slowing you down. Both founders read consulting@renmy.net, and the business co-founder answers the phone.
- consulting@renmy.net
- Phone
- +49 171 3605754