Framer plugin development
Most people who ask for a Framer plugin need one small thing to behave differently, every time, without anyone remembering to do it. We have written three and published them. Install one and judge the work before you hire anyone — including us.
01 — WHAT IS ALREADY OURS
Three plugins on the marketplace, not three screenshots
Anyone can say they build plugins. These are installable today, they were written here, and the free versions take one click.
KUMIHAN
Japanese line breaking. It stops a line from breaking in the middle of a word, which is the single thing that makes a Japanese page look machine-made.
GET KUMIHAN FREE →RUBI
Furigana — the small reading above a name or a rare character. On the web it is normally either missing or hand-placed. This sets it.
GET RUBI FREE →WAEI
The air between Japanese and Latin letters. Too little and the sentence looks cramped; too much and it falls apart. It is a quarter of a space, and it is never automatic.
GET WAEI FREE →We are not asking you to take our word for any of this. That is the point of listing them here.
02 — WHAT A PLUGIN CAN AND CANNOT DO
A plugin runs in the editor. A component runs for your visitors.
This is the distinction that decides whether your idea costs one job or the wrong one. A Framer plugin lives inside the editor: it can read what you have selected, rewrite text and layers on the canvas, insert content, and take a job that someone is doing by hand and make it a button.
What it cannot do is run on the published page. Anything a visitor must trigger — a calculator, a filter, a live feed — belongs in a code component instead.
Tell us the behaviour and we will tell you which of the two it is, before you pay for either. If it turns out you need neither, we will say that too.
03 — HOW IT WORKS
One sentence of scope, one number, two weeks
- — You describe the behaviour in one sentence. If it takes three, it is probably two plugins, and we will split it.
- — We write the scope back to you in writing, with the number, before anything is built.
- — We build it, and you test it on your own project, on your own canvas.
- — You get the source. Publish it privately for your team, keep it internal, or put it on the marketplace under your own name.
From $900
START A PLUGIN →About two weeks from the day the scope is agreed. Wider scopes are quoted after we have seen the behaviour — the number is always fixed before work starts, never after.
04 — WHAT WE NEED FROM YOU
Three answers, and we can quote it the same day
- — What should it do, in one sentence, described as what changes on the canvas.
- — Who runs it: you alone, a team of editors, or a client who will never read a manual.
- — What happens today instead — the manual step it replaces. This is the part that tells us whether the plugin is worth building at all.
05 — QUESTIONS
How much does a Framer plugin cost?
From $900 for a plugin that does one thing well. The number is fixed in writing before anything is built.
What can a Framer plugin actually do?
It runs inside the editor: read the selection, rewrite text and layers, insert content, automate a manual step. It does not run on the published site — that is a code component, and we will tell you which one you need before you pay for the wrong one.
Do we own it afterwards?
Yes. You get the source, and it is yours to publish, keep internal, or submit to the marketplace under your own name. Nothing is held back as leverage.
Can you also build the site it is for?
Yes. A one-page Framer site starts at $900 and a full site from $3,000, handed over on your own Framer account. If the plugin exists to fix something on a site we are building, it is one job rather than two.
You use AI. Where does our material go?
Client material is not put into consumer chat tools and is not used to train anything. We can send our written position on this before you share a single file.
Tell us the one thing that should happen by itself.
CONTACT →