Brand Foundation
A working document of who PlatinumEdge speaks to, what we say, and the language that holds it all together. The strategic spine for the website, sales conversations, and every piece of marketing that follows.
Eight short sections that turn complexity into a story.
This document captures the brand foundation we built from your team's input on the BrandScript questions, the conversations with Sierra and Tim, and the partner voice-of-customer themes. It's the source-of-truth your homepage, sales decks, ads, and email all draw from.
PlatinumEdge sells into two flavors of the same buyer. Some manufacturers come to you before they're on CET because their product is too complicated to fit a standard extension. Others come to you already on CET, with an extension that quietly skipped the complicated parts. The path differs. The cause is the same. This document treats that as the central insight, names the villain, and gives you a complete StoryBrand and a set of PEACE soundbites for both paths.
Every brand needs an antagonist. Yours isn't a competitor.
In StoryBrand, the villain is the force the hero is up against. The hero is your customer. The villain is what's holding them back. For PlatinumEdge, the villain isn't Configura, and it isn't another developer.
It's the developer who quoted the project out because the rules looked too hard. It's the CET extension that worked in the demo but skipped the configurations that matter most. It's the spreadsheet that's been carrying tribal knowledge for ten years because nobody had time to model it properly. It's the dealer who calls every time they hit an edge case the software doesn't handle.
The villain is the failure to honor how the product actually works, and the cost that failure pushes onto sales teams, dealers, and operations leaders who are stuck cleaning up after it. PlatinumEdge exists because complexity should be engineered around, not flattened, not avoided, not handed back to the customer to manage in their head.
Audience 1, the manufacturer not yet on CET.
Tim's stated target buyer. An operations or product leader watching designers spec competitors who are on CET while their own product sits outside the platform.
Their product is configurable, sometimes intricately so, with combinations of dimensions, finishes, options, conditional pricing, and ordering rules. They want it to be available in CET, where designers actually find and specify products. They want their sales team to stop reporting another quarter where projects closed without their product even being considered.
They want their product available in CET, where designers find and specify products. They want their dealers to have a real platform to quote from. They want their sales team to stop watching projects close without them in the conversation. Said plainly, they want their product to compete fairly in the projects designers are speccing right now.
Their product isn't in CET. Designers can't specify what they can't find on the platform, so the product loses spec opportunities to competitors who are. They've gotten quotes from developers, but the complexity pushed scope past what felt reasonable, so the project keeps stalling.
They feel like they're being penalized for having a sophisticated product. They're tired of explaining the same configuration rules to every developer who asks, and quietly outpaced by simpler competitors who got onto the platform first.
A complicated product should not be a barrier to getting onto the platform that designers actually use. The complexity that makes a product valuable should not be the reason it gets locked out of the tools that decide what gets specified.
We've sat across from operations leaders who've been told their product is "too complex" by three different developers. We know what it feels like to watch competitors get specified into projects you used to win, and what it costs your sales team every quarter.
PlatinumEdge has been building inside the Configura and CET ecosystem for over a decade as a recognized development partner. We've turned some of the most complicated configurable products in commercial interiors into clean, dealer-ready CET extensions, and handed off code their internal teams can maintain on their own.
Send a few details through the fit form. We'll tell you honestly whether your product is the kind of work we're built for.
We spend time inside your product's actual rules, configurations, and ordering dependencies before we write a line of code.
Designers can spec it. Dealers can quote it. Your team can trust the output. The platform presence your sales team has been asking for is real.
Your product is in CET. Designers find and spec it as part of their normal workflow. Specifications start coming in for projects you used to lose by default. Your sales team has the platform presence they've been asking for, and they can finally tell their dealer network that the answer changed. Configuration logic that used to live in one engineer's head and one spreadsheet now lives in software your team owns and your engineers can maintain. The revenue line that has been quietly bleeding starts to recover.
Designers keep specifying competitors because that's where the products are. Your sales team keeps watching projects close without you even being considered. Your VP of Sales keeps reporting another quarter where the product line that isn't on CET is leaving real money on the table. Even dealers who like your product start defaulting to the ones easier to quote. Eventually, the lost revenue compounds past the point where catching up is realistic.
Audience 2, the manufacturer already on CET.
The bridge audience. Already on CET, but they're unhappy with what they have. The reasons vary. The dev partner stopped being responsive. Designers complain. Pricing is wrong. Output doesn't match the plant. The specific cause changes from manufacturer to manufacturer. The feeling is the same.
The same operations or product leader, but their CET extension already exists, and they're not happy with it. Maybe the dev partner stopped being responsive. Maybe their designers complain about reliability. Maybe the pricing comes out wrong, or dealers keep hitting cases the software can't handle. The specific cause varies. The feeling is the same: this isn't what they were promised.
They have a CET extension, and it isn't living up to what they hoped for. The reason varies. The dev partner stopped being responsive. The designers keep complaining. The pricing comes out wrong. Cases keep slipping through that the software can't handle. Said plainly, they want an extension that finally works the way it was supposed to, and a partner they can trust to make that happen.
The extension is in place, but the experience isn't right. Designers complain about reliability or output. Dealers hit cases the software can't process. Pricing comes out wrong. Output data doesn't match what the plant needs. Someone internal is spending hours a week cleaning up after the software, fielding dealer questions, or working around bugs. The original dev partner is unresponsive, or no longer feels like the team to fix it.
They're unhappy. The flavor of unhappiness varies, but it's there. Frustration that the partner who built the extension isn't the right one to fix it. Embarrassment when designers or dealers report problems. Fatigue from absorbing cleanup work that should be the software's job. A quiet worry that the original investment in CET was the wrong move. The CET project was supposed to be the answer, and right now it isn't.
A CET extension should leave its users happy. Designers shouldn't have to work around bugs. Dealers shouldn't be calling internal teams for help. The complexity that makes a product valuable shouldn't get flattened in software just to ship faster. The team that built it should have stayed close enough to fix what the real world surfaced.
We've rebuilt enough extensions to know what it looks like when somebody skipped the complicated parts. The cleanup work your team is doing right now is not a personal failure on anyone's part. It's a structural one in how the original extension was built.
PlatinumEdge has spent the last decade in the layer underneath CET, where the real product rules live. We've rebuilt extensions other teams gave up on. We hold higher code standards than most CET partners, which means the extensions we ship are reliable, the pricing is correct, the configurations don't crash, and the code is documented well enough for your team to read and extend.
Walk us through where the current extension stops working through the fit form. We'll be honest about the right move.
We map your product's real configurations, the rules the original extension skipped, and the gaps your team has been working around.
Your extension finally matches your product. Designers trust the output, dealers stop calling for help, and your team owns the code while we stay close to keep it working.
The internal cleanup work that has been quietly costing your team disappears. Dealers trust the output and stop calling for help on cases the software should be handling. Your team stops being the human safety net for the software. The investment you've already made in CET starts paying off the way it was supposed to. Maintenance becomes something your engineers can do, because the code is documented and the rules are visible.
The cleanup work compounds. Trust erodes in two directions. Internally, your team stops believing the system can be fixed. Externally, your dealers revert to phone calls and spreadsheets, which means your product effectively isn't on CET anyway. The original investment becomes a sunk cost. The gap between the product's real rules and the extension gets harder to close every time someone patches around it instead of fixing it.
The same story, compressed for speaking.
PEACE is a five-beat framework: Problem, Empathy, Answer, Change, End Result. These are the lines you can drop into a sales call, a podcast intro, a conference talk, an ad, or a LinkedIn post. Two complete sets, one per audience.
The not-yet-on-CET manufacturer
The CET-rescue manufacturer
The line that holds both audiences together.
When both audiences are in the room, when you're at a tradeshow booth, when a prospect doesn't know yet which path they're on, this is the opener. It's the same logic as the homepage hero, framed as a single spoken beat.
Single-line versions for ads, social, and elevator moments.
When you only have time for one beat. Use these in LinkedIn bios, paid ad copy, podcast intros, sales emails, conference name-tag bios, and the ten-second version of "what do you do."
Audience 1 / Not yet on CET
Audience 2 / Already on CET
The voice and visual rules that hold every PES surface together.
Replicated from the PES Brand Voice and Identity Guide. Print this section, hand it to a copywriter or designer, and they have everything they need to sound and look like PES without you in the room.
The brand in three words.
Every voice and design decision should reinforce these three. If something doesn't, reconsider it.
We do what we say. Clients trust us because we have earned it consistently over time.
Human and approachable. Genuinely invested in our clients' success. Never transactional.
We know our field deeply and we don't oversell it. Expertise speaks through clarity, not volume.
How we show up.
Five personality traits the brand expresses everywhere. Use these as a checklist when reviewing copy or design.
We know our field deeply and don't need to prove it loudly. Confidence, not arrogance.
Approachable and genuinely invested. Never transactional, never cold.
We do what we say. Trust is earned by showing up, not by promising harder.
Organized, clear, and polished in everything we produce. No clutter, no confusion.
Interesting to work with. The kind of brand people actually recommend.
- Stiff or corporate. We don't talk like a policy document.
- Flashy for its own sake. Visual interest serves the message.
- Vague or generic. We say specific, useful things.
- Overpriced-feeling. Confidence, not arrogance.
- Difficult to work with, in tone, in design, or in interaction.
Voice characteristics.
Voice never changes. Tone shifts slightly between contexts (a proposal versus a casual email), but the underlying character stays the same.
Clear, direct language. If a simpler word works, we use it. No jargon for its own sake.
We demonstrate expertise through specificity, not volume. We don't tell people we're the best, we show it.
Friendly and human, but we respect people's time. We get to the point.
We don't overpromise. We say what we mean and mean what we say.
We don't shout. We don't oversell. We state clearly what we offer and why it matters.
Write like this. Not like that.
When in doubt, the left column wins. The right column is what to scrub out of your drafts before you send them.
The color palette.
Cool, professional foundations with warm accents that humanize the brand. Teal leads. Navy grounds. Terracotta and sand keep the system from feeling cold.
What clients should be able to say about us.
Every email, every design, every interaction should reinforce these outcomes. If a piece of communication doesn't earn at least one of these reactions, reconsider it.
The one thing.
If someone walks away from any interaction with the brand and remembers only one sentence, this is the one.
Page rhythm.
The eleven section heads of the new homepage, in order. Read top to bottom and you can skim the whole brand argument in under thirty seconds. This is the brand voice working at the structural level, pulled directly from the Figma design.
- Complexity stopped you?
- Trusted by manufacturers.
- How it shows up.
- We go deep.
- Three clear phases.
- The quiet wins.
- Yes to weird.
- In their words.
- Probably not us.
- Before you ask.
- Tell us what you make.
How to use this brand foundation in your actual marketing.
Concrete plays for the channels PES is most likely to use. Drop these into your editorial calendar, your sales sequence, or your social cadence. They're not finished posts. They're starting points written in the right voice, ready to be tightened and shipped.
LinkedIn posts
For Tim, Sierra, or whoever fronts the brand on LinkedIn. Short-form thought leadership that sounds like a person, not a press release.
-
Post idea 01Designers can't spec what isn't on CET.
Open with the cost of being absent from the platform. Frame CET as where decisions get made. Close with an invitation to talk if complexity is what's keeping a manufacturer off.
-
Post idea 02Three different developers told us our product was too complex. We took it as a compliment.
Founder voice for Tim. About finding the partner who treats complexity as the work, not the obstacle. Personality forward.
-
Post idea 03Your CET extension worked in the demo. Then it met the real world.
Rescue-side post. Names what unhappiness looks like for a manufacturer with a struggling implementation. Empathy plus a specific list of symptoms (designer complaints, dealer calls, output cleanup).
-
Post idea 04Most CET work stops at the surface. We work in the layer underneath.
Differentiator post. Surface vs depth. Catalog symbols vs custom logic. Plain English, no PGC jargon.
-
Post idea 05If your product is simple, you don't need us. That's a good thing.
Self-disqualifier post. Builds trust by being willing to lose the deal that's wrong for both sides.
-
Post idea 06Bring us the spreadsheet. The one with fourteen footnotes.
Playful invitation. Specific, nerdy, warm. Demonstrates the brand voice without saying a word about the brand.
-
Post idea 07We'd rather say no early than take a project that's wrong for both of us.
Trust-through-honesty post. The one PES line a smart prospect should remember.
Blog post topics
Long-form pieces that earn search traffic, support sales conversations, and demonstrate expertise. Each one should land somewhere a prospect can reach the fit form by the end.
-
Topic 01Why your product isn't on CET (and what to do about it).
Diagnostic, audience-1 focus. Walks through the common reasons manufacturers stay off the platform. Ends with a path forward.
-
Topic 02The hidden cost of a CET extension that oversimplified your product.
Audience-2 focus. Names the cleanup work, the dealer calls, the trust loss. Builds the case for rebuild.
-
Topic 03Catalog symbol vs custom extension. Which one your product actually needs.
Educational and qualifying. Helps prospects self-assess before reaching out. Reinforces the "if simple, use a template" honesty.
-
Topic 04What "high code standards" really means for your designers and your dealers.
Translates the technical differentiator into user-side outcomes: reliability, accurate pricing, no crashes, dealer trust.
-
Topic 05Five signs your CET extension was built around the demo, not your product.
Listicle format. Each item is a symptom of an oversimplified extension. Shareable, scannable, recognizable.
-
Topic 06The questions every manufacturer should ask before a CET project.
Buyer's guide format. Educates and pre-qualifies. Lifts cleanly into a downloadable lead magnet.
-
Topic 07Why the developer who built your extension might not be the right one to fix it.
Rescue-prospect post. Sensitive to the political situation of replacing a vendor. Plain-spoken about why a fresh team can be the right call.
Email subject lines
Short, specific, never clickbait. Each one earns the open by sounding like a person noticed something real about the recipient. No exclamation points. No emojis.
-
Cold, not on CETDesigners can't spec what isn't there
States the cost in eight words. Use for outreach to manufacturers visibly absent from CET.
-
Cold, genericAbout your CET situation
Generic enough to open, specific enough to feel personal. Pairs well with rescue prospects.
-
Cold, recognitionHave you been told your product is too complex?
Recognition hook. Lands for any prospect who has had at least one bad developer conversation.
-
Cold, rescueIf your extension worked in the demo but not in the wild
Audience-2 specific. Self-qualifying. Only opens for the right reader.
-
Cold, rescueWhen your team is the safety net for the software
Names the silent cost of internal cleanup. Audience-2 emotional opener.
-
NurtureA short note on what we'd do first
Implies a plan without overpromising. Use after a discovery call.
-
NurtureOne more thought on your product
Personal, low-pressure. Use to follow up after a quiet stretch.
-
Re-engagementBringing this back to the top of your inbox
Honest about being a follow-up. No pretending.
Email body templates
Cold outreach and nurture sequences in the right voice. Customize the bracketed variables. Keep the rhythm. No buzzwords.
-
Cold outreach, not on CET
Hi [Name], I noticed [Manufacturer] isn't currently in CET. Most commercial-interior designers spec products from CET during their workflow, which means a product not in the platform tends to get passed over by default, even when it's the better option. We build CET extensions for manufacturers whose products are too complicated for standard catalog symbols. If complexity has been the reason you're not on the platform, it might be the reason to call. Worth a fifteen-minute fit conversation?
[Sender] -
Cold outreach, on CET but unhappy
Hi [Name], A lot of the manufacturers we talk to have a CET extension already. They didn't come to us because the extension is broken. They came because they're unhappy with what it gives them. Maybe their designers complain. Maybe pricing comes out wrong. Maybe their team is quietly cleaning up after the software. The original developer might be unresponsive, or might just not feel like the right team to fix it. If any of that sounds familiar, we should talk.
[Sender] -
Nurture follow-up after discovery
Hi [Name], thinking about the conversation we had [last week]. The piece that stuck with me is [specific complexity they mentioned]. That's actually the part of your product we'd be most interested in. Most developers see something like that and quote it out. We'd want to spend an hour mapping it before we said anything about scope. If you're open to that, I'll send a calendar link.
[Sender] -
Post-call recap
Hi [Name], short recap of what we talked through. You're [current state, e.g., not yet on CET, or on CET with X frustrations]. We'd want to start with [Phase 1 description]. Realistic timeline is [range]. The next decision is whether your team is ready to map the configuration logic with us. If yes, here's a calendar link. If you'd rather think on it, that's fine too.
[Sender]
Social media posts
Short captions for Instagram, X, and the LinkedIn company page. The brand voice condenses cleanly into one or two lines. Pair each with a strong image or a single typographic asset.
-
Caption 01Bring us your hardest product. We mean that as a compliment.
Eight-word personality post. Pairs with a photo of the team or the office.
-
Caption 02If your product fits in a catalog symbol, we're overkill. That's a good thing.
Self-disqualifier in social form. Counterintuitive, memorable, on-brand.
-
Caption 03Most CET work stops at the surface. Not ours.
Tight differentiator. Could anchor a carousel about the layer-underneath story.
-
Caption 04Complexity? Solved.
Brand tagline. Use as a closer on most company-page posts. Pairs with any visual.
-
Caption 05Tim's whole thing. It looks complicated. This sounds like fun.
Founder personality post. Direct echo of how Renee describes him. Earns trust through honesty about who runs the team.
-
Caption 06A spreadsheet that fourteen people understand differently. We turn that into software.
Specific, nerdy, recognizable. Captions a photo of the kind of doc PES often inherits at the start of a project.
Sales conversation openers
Lines for discovery calls, conference booths, and warm intros. Designed to open a real conversation in twelve words or fewer.
-
Discovery openerTell us the weird thing about your product.
The single best opener for a discovery call. Invites the prospect to surface real complexity in their first minute. Self-qualifying.
-
Rescue openerWhere does your current extension fall apart?
Audience-2 opener. Skips the small talk. Goes straight to where the unhappiness lives.
-
Aspirational openerIf you weren't worried about scope, what would you want CET to do?
Useful when a prospect has been gun-shy because previous quotes felt unreasonable. Lets them dream.
-
Expertise signalWhat's the part nobody on your team has fully written down?
A signal-of-expertise question. Demonstrates understanding of how configurable products actually work in real companies.
-
Self-qualifying openerIf your product is simple, you don't need us. Walk me through where it stops being simple.
Honest, charming, lets the prospect lead. Doubles as a qualification check.
-
Booth openerAre you on CET yet, or is that part of why you stopped by?
For trade shows. Self-qualifying without being aggressive. Routes the conversation into one of the two paths immediately.
This is a working document, not a wall hanging.
The BrandScripts, PEACE soundbites, and channel plays here are the source of truth for the homepage we're rebuilding, the sales conversations your team is having now, and every piece of marketing that follows. Pull from it. Repeat the lines. Trust the framing. Tell us where it bends, and we'll sharpen.