I Migrated From Salesforce to Figma and My MRR Doubled. Here's How.

I’m going to say something that might get me kicked out of the Silicon Valley founder’s club. For years, I thought running a real business meant running on Salesforce. It was the undisputed king, the default choice for any startup that wanted to be taken seriously. And for a while, I drank the Kool-Aid. We were a Salesforce shop, and I thought that meant we had made it.

Boy, was I wrong.

It started with a slow burn. A nagging feeling that something was off. Our sales team, a group of absolute killers, was spending more time fighting with the CRM than actually selling. Deals were getting stuck in weird, unexplainable stages. Reports were a nightmare to generate, and when they finally landed on my desk, I couldn’t make heads or tails of them. We were paying a small fortune for a tool that was actively working against us. The final straw? I saw our monthly bill. We were burning through $15,000 a month for a glorified spreadsheet that everyone hated. That’s $180,000 a year. For what? So we could say we used Salesforce? It was insane.

I’m a builder. I’ve built and sold two companies, RemoteTeam and MovieLaLa. I’ve invested in over 200 startups, including some you might have heard of like Anthropic and OpenAI. I’ve seen what works and what doesn’t. And what I was seeing with Salesforce was a whole lot of ‘doesn’t’. It was a relic of a bygone era, a bloated, enterprise-first behemoth that had no place in a fast-moving startup. We needed something nimble, something that could keep up with our pace of innovation. We needed a tool that our team would actually want to use.

So, I did something that made my investors raise their eyebrows and my advisors question my sanity. I decided to migrate our entire sales process from Salesforce to Figma.

Yes, you read that right. Figma. The design tool.

People thought I was crazy. “But Sahin,” they’d say, “Figma is for designers. It’s for making pretty pictures. You can’t run a sales process on a design tool.”

To which I’d reply, “Watch me.”

The Unbearable Heaviness of Salesforce

Before I get into the how, let’s talk about the why. Why would a sane founder even consider a move like this? To understand that, you need to understand the pain of being a startup in the Salesforce ecosystem.

Salesforce is a universe unto itself. It’s powerful, no doubt. But that power comes at a cost. And I’m not just talking about the exorbitant licensing fees. I’m talking about the cost of complexity. The cost of a thousand features you’ll never use. The cost of an ecosystem designed to lock you in and bleed you dry.

For a startup, speed is everything. You need to be able to pivot on a dime, to experiment with new sales motions, to get your product into the hands of customers as quickly as possible. Salesforce, with its rigid structure and endless customization options, was the antithesis of speed. It was a lead weight tied to our ankles.

I remember one time we wanted to change a simple field in our lead object. A tiny, insignificant change. In any sane world, this would have taken five minutes. In the world of Salesforce, it took two weeks. Two weeks of meetings with a certified Salesforce consultant (at $200 an hour, I might add), of navigating a labyrinthine admin panel, of praying that we didn’t break something in the process. It was a soul-crushing experience. And it was happening all the time.

I’ll never forget the one that got away. We had a seven-figure deal on the line with a Fortune 500 company. It was a company-maker. The champion on their side was pushing hard for us, we had verbal commits, and everything was lined up. Then, silence. For a week. We were scrambling, trying to figure out what happened. It turned out our main contact had gone on an unexpected medical leave, and the handover notes were buried somewhere in a custom Salesforce object that no one on our team even knew how to access. By the time we figured it out and connected with the new stakeholder, they had already signed with our competitor. A seven-figure deal, gone. Just like that. Not because our product was inferior. Not because our team didn’t hustle. But because our CRM, the very tool that was supposed to be our single source of truth, had failed us in the most spectacular way possible. That night, I couldn’t sleep. I just kept thinking about that $180,000 a year we were paying for the privilege of losing our biggest deal ever. That was the moment the slow burn turned into a raging fire.

Our sales team, the lifeblood of our company, was miserable. They were spending hours every day on data entry, on wrestling with a clunky interface, on trying to make sense of a system that seemed designed to confuse them. They weren’t selling. They were being held hostage by their tools. And it was showing in our numbers. Our sales cycle was getting longer and our close rate was dropping. As a result, our MRR was stagnating. Something had to change.

The Figma Epiphany

The idea to use Figma didn’t come to me in a flash of inspiration. It was born out of desperation. I was in a meeting with our design team, watching them work their magic in Figma. They were collaborating in real-time, building complex interfaces with a speed and fluidity that I had never seen before. They were happy. They were in their flow. And it hit me. What if we could bring that same energy, that same sense of flow, to our sales process?

I started to play around with the idea. I created a new Figma file and started to map out our sales pipeline. I used frames to represent the different stages of a deal. I created components for our customer profiles, our deal notes, our contact information. I used comments to track our communication with customers. It was all there. Everything we needed to run our sales process, right inside a tool that our team already knew and loved.

I’ll be honest, I had no idea if it would work. It was a wild, harebrained experiment. But we were desperate. We had to try something. So, I pulled our head of sales aside and showed him what I had built. He was skeptical at first. But as I walked him through the flow, I could see a glimmer of hope in his eyes. “You know,” he said, “this is actually… not a bad idea.”

That was all the encouragement I needed. We decided to run a pilot program with a small group of our sales reps. We told them to ditch Salesforce for a week and run their entire process out of Figma. The results were astounding.

The Great Migration

The pilot was a resounding success. The reps who used Figma were closing deals faster and were visibly more engaged and happy. The feedback was unanimous: “This is so much better than Salesforce.”

So, we made the call. We were going all-in on Figma. We gave ourselves one month to migrate our entire sales process. It was an ambitious timeline, but we were determined to make it happen.

We started by exporting all of our data from Salesforce. It was a messy, painful process. But we got it done. Then, we started the process of importing that data into Figma. We created a master file for our sales pipeline, with a page for each quarter. We used the Figma API to automate the creation of our deal frames. We set up a system of tags and labels to track the status of each deal. It was a lot of work, but it was also incredibly empowering. We were building a system that was tailored to our exact needs, not the other way around.

Our Figma CRM: The Nitty-Gritty

So what did this Rube Goldberg machine of a CRM actually look like? It was surprisingly simple, which was the whole point. Here’s a breakdown of the core components:

• The Pipeline View: This was the main dashboard. We created a huge Figma canvas, and each deal in our pipeline was a top-level Frame. We named each frame with the client’s name and the deal size, like ACME Corp - $150k ARR. This gave us an instant visual overview of our entire pipeline. No more clicking through endless list views.

• Deal Stages as Columns: We organized the deal frames into columns that represented our sales stages: New Lead, Initial Contact, Demo, Proposal Sent, Negotiation, and Closed-Won/Closed-Lost. Moving a deal from one stage to the next was as simple as dragging and dropping a frame. It was so satisfying. The sales team made a game out of it.

• The Deal Frame: This is where the magic happened. Each deal frame was a self-contained dossier for that customer. We created a component for our standard deal layout. It included:

  • Customer Info: A text block with the key contacts, their titles, and contact information.
  • Deal Notes: A running log of every interaction. We’d just add a new text box with the date for each new note. It was like a mini-feed for each deal.
  • Next Steps: A clear, bolded text box at the top of the frame that said NEXT STEP:. This forced the reps to always define the single most important next action.
  • Health Score: We used a simple traffic light system with colored dots (Green, Yellow, Red) to indicate the health of the deal at a glance.

• Automation with the Figma API: This was the secret sauce. We didn’t want to be doing a ton of manual data entry. I’m an engineer at heart, after all. I wrote a few simple Python scripts that used the Figma API to do things like:

  • New Lead Ingestion: We used a Zapier webhook to listen for new leads from our website’s contact form. When a new lead came in, the script would automatically create a new deal frame in the New Lead column in Figma, pre-populated with the information from the form.
  • Reporting: I wrote a script that would run every night, scan the entire Figma file, and generate a simple MRR forecast. It would look at the deal size, the stage, and our historical close rates to spit out a number. It was more accurate than our Salesforce reports ever were.
  • Archiving: When a deal was moved to Closed-Won or Closed-Lost, another script would automatically move it to an archive page in the Figma file to keep our main pipeline view clean.

This setup wasn’t perfect. It didn’t have all the bells and whistles of Salesforce. But it had something much more important: clarity. For the first time, our entire company could see our sales pipeline. Our engineers could see the deals that were in flight. Our marketing team could see which campaigns were generating the most valuable leads. It broke down the silos between our departments and got everyone aligned around the same goal: closing deals.

Of course, it wasn’t all smooth sailing. There were moments when I thought we had made a terrible mistake. I remember one late night, a week before our go-live date, when our entire Figma file crashed. I had a mini-meltdown. I thought we had lost everything. But the Figma support team was amazing. They helped us recover our file and get back on track. It was a stressful experience, but it also reinforced my belief that we had made the right choice. We were working with a company that actually cared about its customers.

Finally, the day came. We officially turned off Salesforce and moved our entire sales team over to Figma. There was a sense of excitement and trepidation in the air. We had taken a huge leap of faith. And we were about to find out if it had paid off.

The Aftermath: A New Era of Sales

The first few weeks were a bit of a learning curve. But our team was so motivated to get away from Salesforce that they embraced the change with open arms. And the results were immediate and dramatic.

Our sales cycle, which had ballooned to over 90 days with Salesforce, dropped to under 30 days. Our close rate, which had been hovering around 15%, shot up to over 30%. And our MRR? It doubled. In three months. It was the kind of growth that I had only dreamed of. And it was all because we had the courage to ditch a tool that wasn't working for us and embrace a new way of thinking.

But the benefits weren’t just financial. Our sales team was transformed. They were no longer data entry clerks. They were creative problem-solvers. They were using Figma to build custom proposals for our customers, to collaborate with our design team on new product features, to create a more visual and engaging sales experience. They were having fun. And it showed in their performance.

We even started using Figma for our investor updates. Instead of a boring old PDF, we would send them a link to a Figma file with interactive charts and graphs. They loved it. It was a small thing, but it showed them that we were a company that was thinking differently.

So, Should You Ditch Your CRM for Figma?

Look, I’m not saying that every company should ditch their CRM and move to Figma. That would be insane. But I am saying that you should question the default choices. You should challenge the status quo. You should find the tools that work for you, not the other way around.

For us, that tool was Figma. It gave us the flexibility and speed we desperately needed, along with a new sense of creative freedom, to take our business to the next level. It changed everything for us. And it all started with a simple question: “What if there’s a better way?”

If you’re a founder who is feeling the pain of a bloated, expensive CRM, I urge you to ask yourself that same question. You might be surprised by the answer. And if you're looking for more ways to optimize your startup, check out my post on the best SaaS tools for early-stage startups.

It won’t be easy. People will think you’re crazy. But the rewards are worth it. Trust me. I’m living proof.

Frequently Asked Questions

Can I switch later if I make the wrong choice?

In most cases, yes. The switching cost is usually lower than people fear. The bigger risk is analysis paralysis, spending months evaluating options instead of picking one and learning from real usage.

Which option is best for startups?

It depends on your stage, budget, and specific needs. Early-stage startups should prioritize flexibility and low cost. Growth-stage companies can afford to optimize for performance and scalability. There's no universal answer.

What factors matter most in this comparison?

For most founders, the three factors that matter most are: total cost of ownership, ease of implementation, and how well it integrates with your existing workflow. Features are important but often overweighted in decision-making.

How often should I re-evaluate this decision?

I recommend revisiting major tool and strategy decisions every 6-12 months. The landscape changes fast, and what was the best choice a year ago might not be today. But don't switch for the sake of switching.