Hi, I’m Vitalii. I build CraftForms, and I answer your emails myself.
I’ve been building WordPress plugins since 2009, with a proven track record: Uni CPO, my product configurator for WooCommerce, has more than 26,000 installs. CraftForms is what ten years of answering its support emails taught me.
- Developer
- Vitalii Kiiko
- Based in
- Cagliari, Sardinia
- Building since
- 2009
- Write to me
- Email me
In numbers
| WordPress since | 2005, with a personal blog and a Left 4 Dead fan site |
|---|---|
| Professional since | 2009 as a freelancer, first WordPress client in 2010 |
| Also built | Uni CPO, a product configurator for WooCommerce, and Builderius, a visual site builder I co-founded |
| Support | From me, on every plan, the free one included |
How I got here
I’ve built for the web professionally since 2009, and for WordPress since my first client project in 2010. Early on I chose code over visual design: interfaces that move, calculate and respond to the user. That focus has shaped everything I’ve made since.
I started by selling WordPress plugins on Envato and became an Elite Author, the status Envato gives its top-selling authors. I ran HighSea Studio, a WordPress theme studio, and co-founded MooMoo, a web studio where I still build web apps and static sites for clients.
In 2016 I released Uni CPO, a product configurator for WooCommerce. It has grown to more than 26,000 installs and 2,500 paying customers, with a 4.6/5 rating on WordPress.org. Uni CPO has its own visual builder. I kept improving and upgrading it, and it grew into the engine of Builderius, the visual site builder I co-founded with Volodymyr Denchyk and Elvis Krstulovic. The front-end components in that builder are some of my best work so far.
CraftForms brings that experience together: more than fifteen years of client work, a configurator trusted by thousands of stores, and a site builder. It’s a new-generation form builder that runs on the Gutenberg block editor engine and is built around the most refined form components I’ve made.
Why a form plugin
Forms are where a website does business. It’s the moment a visitor stops reading and acts: asks a question, books a time, designs a product, pays. The same building block carries very different jobs:
- Contact and quote requests that reach the right inbox and get a branded reply.
- Bookings with real availability, payments and calendar sync.
- Product personalisation with live prices and an interactive preview of what the customer is building.
- Orders and payments, with invoices, tickets and confirmations generated as PDFs on submit.
Most form plugins are built for the first job and stretched to cover the rest. I’ve spent years at the hard end of that list, on pricing logic, configurators and the data that has to be right after Submit. CraftForms is built for every one of these jobs from the start.
What ten years of Uni CPO support taught me
I’ve answered Uni CPO’s support emails myself for ten years, across thousands of stores. The same lessons came up again and again, and each one is now built into CraftForms:
- Shared options must not break other products. In Uni CPO, changing a global “width” option for one product changed it for every product using it. In CraftForms one form serves many products, each with its own prices. One client runs a single form across 109 products.
- The price the customer sees must be the price charged. The same calculation runs in the browser and on the server.
- Most of the work happens after Submit. Store owners spend 5% of their time building a form and 95% handling what comes in. Bookings, payments, PDFs, emails and orders are built in, not sold as add-ons.
- Sites outgrow their stack. Your forms aren’t tied to WordPress: build them there and use them on static sites, or on CraftForms Cloud.
Will it still be here?
That’s the right question to ask before you build ten client sites on something. My answer:
- Track record. Uni CPO has been on WordPress.org since 2017 and still gets updates. I don’t abandon products.
- It’s independent. CraftForms is funded by its customers, through yearly licences and Cloud subscriptions. There are no investors waiting for an exit.
- You keep your data either way. Submissions export to CSV and JSON, published forms keep working if a yearly licence lapses, and the code is GPL.
How to reach me
Write to support@craftformswp.com. I read every message and answer it myself, usually the same day. On the paid plans, the first setup is on me.
Featured in The Builderius Story on WebTNG. Elsewhere: LinkedIn, and MooMoo for my client work.