The Presentation Was Locked and No One Could Edit It
We had a company presentation that had been living as a PDF for longer than it should have. The original designer built it in Figma and then left the company, taking all the working knowledge with them. What remained was a polished PDF and a Figma file that was roughly 70% aligned with it — useful as a reference, but not a clean starting point.
The business problem was straightforward: anyone who needed to update a slide, swap a logo, or adjust a number had to request a new export or work around the locked format. That's not sustainable when a presentation is used across multiple teams. We needed the whole thing rebuilt in Google Slides — pixel-perfect, fully editable, and ready for anyone in the company to maintain going forward.
I looked at what that actually required and immediately understood this wasn't a quick copy-paste job. Getting it right would take precision I didn't have time to apply myself.
What I Discovered the Rebuild Actually Involves
My first assumption was that the Figma file would make this faster. It does — but only partially. Because the Figma file was 70% aligned with the current PDF, the remaining 30% still needed to be reconstructed by reading the PDF directly, matching spacing, font sizes, color values, and layout structures slide by slide.
That gap is where the real work lives. Google Slides doesn't import Figma files natively, so every element — text boxes, shapes, image crops, icon placements — has to be manually placed and sized within Google Slides' grid system. Fonts used in Figma may not exist natively in Google Slides, which means finding acceptable substitutes that preserve the visual weight and line spacing of the original.
Beyond layout, there's the matter of master slides and theme consistency. A properly rebuilt deck uses slide masters so that headers, footers, and background elements behave consistently across all slides — not just visually, but structurally, so future editors don't accidentally break the layout by clicking on the wrong layer. That infrastructure takes deliberate setup, not just visual matching.
The Work That Needs to Happen to Get This Right
The first layer of the work is a full audit and mapping exercise. Every slide in the PDF needs to be catalogued — its layout type, text hierarchy, image placement, and any design elements that don't exist in the Figma file. A disciplined practitioner approaches this like a translation project: identify what exists in the source, categorize what's available from the Figma reference, and flag every gap that needs to be reconstructed from scratch. That audit typically reveals that the "30% missing" is unevenly distributed — some slides are fully reconstructable while others require close reading of pixel-level spacing decisions. Without the audit, rebuilds drift from the original in ways that aren't obvious until the deck is printed or presented.
The second layer is the visual mechanics work inside Google Slides itself. Setting up a proper slide master means establishing a 12-column layout grid, defining a type hierarchy — typically title at 36pt, subhead at 24pt, body at 16pt — and locking background elements so they can't be accidentally edited by non-design users. Color values from the original PDF need to be extracted precisely (HEX codes or RGB values, not eyeballed), applied to a theme palette of no more than four to five brand colors, and propagated consistently. This setup phase takes longer than most people expect, especially when the source is a flat PDF with no style metadata to reference.
The third layer is polish and consistency validation across all slides. Once the initial rebuild is complete, the deck needs a full pass where every slide is checked against the original PDF at 1:1 scale — spacing between elements, margin uniformity, icon alignment, text wrapping behavior. A single misaligned element on a master slide can cascade across a dozen slides without being obvious until someone views it at full screen. This validation round is often skipped by non-specialists, and it's precisely where a professionally rebuilt deck earns its quality difference from a rushed one.
Why I Brought in Helion360 to Handle It
When I mapped out what this project actually required — the audit, the master slide setup, the pixel-level matching, the validation pass — I recognized immediately that this wasn't work I could absorb into my week. The technical depth alone would have taken me days just to get oriented, let alone execute at the quality level the presentation needed.
Helion360 handled the full project end-to-end. They worked directly from the PDF and the Figma reference file, completed the audit and gap analysis, built out the Google Slides master structure, and reconstructed every slide to match the source presentation with the precision the project demanded. The turnaround was fast — done in days, not weeks — and the output came back ready for Phase 2 improvements without any rework needed on the foundation.
What made the difference was that the tooling and process were already in place. There was no learning curve on their end, no time lost figuring out how to approach the Figma-to-Google-Slides conversion. They do this work routinely, and that showed in the speed and accuracy of the delivery.
The Result and What I'd Tell Anyone Facing the Same Situation
What came back was a fully editable Google Slides deck that matched the original PDF presentation at a level our team couldn't distinguish from the source. Every slide was built on a clean master structure, fonts were properly substituted and consistent, brand colors were pulled accurately, and the layout held up at full-screen presentation resolution. The deck was immediately usable — by anyone on the team, with no design background required.
Phase 2 — the improvements we wanted to make — started from a clean, solid foundation, which meant those conversations were about content and strategy, not fixing the rebuild.
If you're looking at a similar situation — a PDF that needs to become a living, editable Google Slides presentation — Helion360 is the team I'd engage. They delivered fast, handled every layer of the execution, and handed back a deck that was genuinely ready to use.
For more examples of presentation transformation work, see how I transformed bland Google Slides into engaging presentations with dynamic design.