Secure Digital Promotions

Two founders came out of a company that was winding down and started their own. They brought real experience in the industry, a name they believed in, and a site they built themselves.

The site did the plain job well. It listed the company’s services, and stated them clearly. The read that came back from people they showed it to was often some version of the same thing, that it looked like a site built by a capable executive. It was. The next step was to look like the company they were building.

The founders arrived with Secure Digital Promotions, the promise stated plainly. What it needed was an initialism that could hold the identity on its own at the sizes a brand lives at, a favicon, an app tile, a sponsor row, the corner of a slide.

The mark is two layered curves that trace an S without ever drawing one. It stays abstract enough to work as infrastructure and specific enough to be recognizable. The two loops interlock without merging, which is what SDP sits between, a brand on one side and the people entering its promotions on the other.

The wordmark does the same job in type. Secure is set heavy and Digital Promotions light, so the promise carries the weight and the category recedes. Gogh ExtraBold for the monogram, Inter for the wordmark, geometric where it needs presence, neutral where it needs to disappear into an interface.

Four lockups, each with a job rather than a preference.

Digital is in the name, and the first drafts took that literally, pixel grids and screen static and the rest of the obvious moves. They looked like clip art. What worked was the opposite instinct, structure with flow still in it, and the two colors that mark landed on are the two the entire brand was built from.

Green is doing two jobs at once. It puts something organic against all that structure, and up in the lime range it reads cyber rather than natural. That is the brief answered in a color instead of a sentence, human enough to approach and built enough to trust.

By then I had designed enough brands to know what blue does. It reads as trust, and as corporate and professional, and it does that before anyone notices it is doing anything. Drawing a mark for a venture firm years earlier I had gone bank to bank and found the same answer nearly every time. Blue went in, and it happened to sit well next to the green. Across this category the color story was either generic or absent, so a committed pair was itself a position.

From there the palette runs out in two families, greens from lime through forest, blues from cyan through royal and down into navy. Navy is the same blue at the dark end. The two families overlap at teal, and that overlap is what lets a gradient cross from one to the other without a seam.

SDP sells a service, but the promise underneath it is operational: entries verified, rules enforced, results reported. The site’s visual language borrows from the categories buyers hand that kind of promise to.

SDP stood up a WordPress site themselves so they had something to send while the build question stayed open. They came back wanting what they had wanted from the start: a visual direction that made the whole thing read as one company, with the storytelling flow they came in with carried all the way through.

The direction was written for that build. A section-level framework, the seven-part narrative above, a visual job and an allowed-and-refused list per section, and an explicit split between what was worth finalizing now and what should wait. All of it scoped to work inside WordPress with static vector assets, because that was the build that existed.

What I gave was directional: layout, placement, and what each section had to accomplish, worked into what they had up. The build itself stayed theirs.

One constraint ran throughout the project. What a designer hands over is a design, a demo, and someone else has to turn it into a live site, a product. Every version had to bend around that. The first waited on a developer whose time was already spoken for. The second traded brand for a handoff that would pass. The third got built by the client themselves on a CMS, because they needed something live.

Then two things landed at once. AI got good enough to build a real front end, and Figma shipped a native MCP server. The second one matters more than it sounds. Before it, the loop only ran one way, and asking for one small change meant an AI tore the whole build down and started again, usually breaking something else on the way. Whatever it produced could not be brought back into Figma to be edited, so you were stuck with what it gave you.

The MCP closed the loop. A design idea becomes code, code is visually translated as an editable Figma file, which can be further refined into real components and variables. If needed, a single button can be pulled out, fixed, and put back without rebuilding the whole page around it. The design and the build stopped being two artifacts handed between two people.