If you've been told what you want isn't possible on your platform, or you've been quoted a rebuild on a custom framework to get one feature, this page is for you.
what i build
What I build
Member portals and gated content
Logins where different people see different things: client dashboards, resource libraries, paid areas, internal tools.
Database-driven pages
One template that generates hundreds of pages from a data source: locations, staff, inventory, listings, product catalogs. Build a dozen by hand and you'll never do it again.
Integrations with software you already run
Your CRM, inventory system, scheduling tool, accounting platform. If it has an API, your site can talk to it directly instead of someone rekeying data between them.
Workflow automation
If a person on your team does the same thing every week because the website can't, that's usually a scheduled job that runs at 2am instead.
Custom forms and logic
Multi-step quoting, conditional questions, routing to the right person, calculations that a standard form can't do.
how it's possible
What makes this possible
Wix has a development platform called Velo: JavaScript front and back, a real database layer, npm packages, HTTP functions for external APIs, and scheduled jobs. It's a full development environment, not a "custom CSS" box.
​
Most people, including a lot of developers, don't know it exists. They evaluate the drag-and-drop editor, conclude the platform is a toy, and quote you a rebuild. That gap is most of my custom work.
honest
When you don't need me
Worth saying plainly, because roughly half the people who ask for custom development don't need it.
Contact forms, booking, and online stores
These are mature built-in features. Custom-coding them is almost always wrong.
Design changes
That's the editor's job, not code.
If an existing app does 80% of it
Run that for a month before paying for the last 20%. You may stop caring.
I check for all of the above before quoting custom work. Telling you that you don't need something is cheaper for both of us than building it.
​
If you want the longer version of this decision, I wrote it up: when you need Velo and when you don't.
what drives cost
What drives the cost
Custom work is quoted per project, because the same request can be an afternoon or a month.
How many systems it touches
Something self-contained is straightforward. Something syncing with your CRM, inventory, and accounting is three integrations, each with its own failure modes.
Whether your data is already structured
If it's organized, building on it is fast. If it lives in five inconsistent spreadsheets, cleaning it is most of the job.
Whether it has to keep running
Something that runs once is cheap. Something that runs nightly, handles errors, and tells you when it breaks is real software.
Whether anyone else has to maintain it
Code written to be handed off takes longer to write and saves you money the first time someone else touches it.
a warning
A warning about inherited code
I clean this up regularly: custom code written without documentation, by someone you can no longer reach, is expensive to take over.
​
Before hiring anyone for custom work, me included, ask what happens if you stop working together. You should own the code, roughly understand what it does, and be able to hand it to someone else. If you can't get a straight answer, that is the answer.