About
Built by engineers who have lived through every shift.
Paladin was founded by an engineer from Salesforce R&D to bring platform-level depth to enterprise teams. We helped companies move from installed software to SaaS. Now we help them move from SaaS to AI, without lowering the bar.
Founder
Nikita Prokopev, founder
Nikita started coding at 12. He studied computer science at the University of Illinois at Urbana-Champaign, where he worked at the National Center for Supercomputing Applications, and joined Salesforce during his master’s degree.
Over nearly nine years in Salesforce R&D he built the first native CPQ application on the platform, before Apex and Visualforce shipped. He helped bring the Metadata API to life, and worked on My Domain, Visualforce, application security and Salesforce’s first cloud security scanner. He started Paladin to bring that depth to clients.
Three shifts
We do our best work when the ground moves.
Software → SaaS
Nikita joins Salesforce R&D and builds on the platform before Apex exists.SaaS at scale
Paladin is founded: CPQ, managed packages and integrations for Salesforce teams, then every Salesforce cloud and the systems around it, from SAP to NetSuite.SaaS → AI
AI Delivery launches. Every change we ship is drafted with AI and reviewed by a senior engineer.Offices
Three offices, one team.
San Francisco
2021 Fillmore St, Suite 1335San Francisco, CA 94115 09:00Engineering · Israel timeTel Aviv
Tel Aviv, Israel 19:00Delivery centre · Central European timeWarsaw
Warsaw, Poland 18:00Clocks show local time when it is 09:00 in San Francisco: Warsaw is finishing its day and Tel Aviv is about to pick up the work.
Values
What we hold ourselves to.
Say what it will take. Then do it.
No optimistic estimates to win the deal, and no easy yes to keep the peace.Leave it better than we found it.
Less code, clearer systems, fewer surprises for whoever comes next.Taste and judgement, machine speed.
AI does the repetitive work. People decide what good looks like and make the calls.Teach, don’t trap.
Your team should be able to run what we build without us.Work with people who have done it before.
30 minutes with a principal engineer. You leave with scope, team shape and a first milestone.