← All projects
Studio · Platform · 2004 – Present

FlexEdit

The publishing platform Smartflex was founded on: clients edit their website on the live page itself, while the designer’s markup stays locked. Built in 2004. Still in production.

Product design On-page editing Multi-tenant platform 21 years live
2004
First release
21
Years in production
1000s
Sites built on it
0
Admin backends to learn
The bet

The website is the CMS

In 2004, a small business that wanted to update its own website had two bad options: a blog-style admin backend that looked nothing like the site, or desktop software and an FTP login — which meant one wrong click could destroy the layout.

FlexEdit made a different bet. There is no backend. The client visits their own live website, logs in from a link in the footer, and the page itself becomes editable — pencil icons appear beside the text and images the designer chose to open up, and nothing else.

That second half was the real idea: the designer decides exactly what is editable. Clients got the freedom to keep their content fresh; designers kept the integrity of the work. Neither had to trust the other with more than they should.

How it worked

Edit in place, publish in place

Pages stayed ordinary hand-authored markup. The designer marked each editable region with a token — {$txt1.60.3$} — that set not just where the client could type, but how big the editing surface would be.

Everything the client touched happened on the page: click a pencil, edit in a rich-text window, watch the page update in place, hit save. A brand-new page seeded itself with “This text is editable — click LOGIN to get started,” so the empty state was the onboarding.

01

Log in on the live page

No separate admin URL. A footer link switches the same page into edit mode, with pencil icons beside every editable region.

02

Designer-controlled regions

Token markup defines what clients can edit and how much room they get. The layout, styling, and everything else stays locked.

03

Live in-page preview

Rich-text editing with spellcheck in six languages and paste-from-Word cleanup. Changes appear on the page instantly, before anything is saved.

04

A product, not a tool

Image library, slideshows and galleries, PayPal buy-buttons, newsletter signups, file downloads, and per-page SEO fields — self-serve, with video tutorials built into the help buttons and the support library.

Editing in place — a menu item rewritten on the live page, saved, and published without leaving it
The business

One engine, many storefronts

FlexEdit wasn’t sold as software — it was run as a service. One multi-tenant install served every site from a shared platform, with content keyed per account and per page.

On top of the engine sat turnkey product lines for specific professions — yoga and personal training above all, alongside acupuncture, massage, and coaching — each a niche brand offering a designed site the owner could safely maintain alone. The fitness lines were built on direct affiliate relationships with some of the largest organizations in personal training, with custom offerings for the members of NSCA, PTN, and canfitpro, among others. New sites went to clients on staging domains for review before launch, and hosting made the revenue recurring.

The platform carried the studio to a ten-person team, run fully remote from 2004 — years before distributed companies were ordinary.

Longevity

Still running, 21 years on

The industry eventually arrived at FlexEdit’s ideas: on-page editing became the norm with Medium and Squarespace around 2012 and reached WordPress with Gutenberg in 2018. Constraining what clients can touch is now just called a design system.

The platform itself never stopped. The same codebase has been actively maintained across four PHP eras, two database generations, and the death of Flash — and sites built on it are still live today. It remains the studio’s original proof of practice.

Not everything survived the journey. The video tutorials sitting behind every help button were built in Flash, and when Flash died the whole training layer had to come out with it — a feature lost to a platform decision made somewhere else entirely. Twenty-one years is long enough that some of what you build gets taken away from you.

4
PHP eras spanned
2
Database generations
10
Person remote studio
≈8
Years ahead of the industry
← Back to
All projects