Form design
You can spot most funnel builders by their forms. Same tiles, same rounded corners, same button in the bottom right. Convenient for the vendor. Less so for your brand, and for an agency building on a client brief it is often the reason the tool never gets proposed. asksteps offers two ways out of that, and you can take both in the same form.
Both are in every plan, the free one included.
Colors, typeface, corner radii, border weight, shadow, width, how the answers are arranged, the progress indicator. All of it through color pickers and dropdowns, with a live preview. Thirteen themes are there as a starting point; what you make of them you save as your own.
For anything no form element covers, drag a free section into the form and write HTML and CSS into it. Pricing table, comparison grid, callout box, an input layout with a next button of your own.
The free section knows your theme colors. Change the theme and it changes along, instead of sitting there in the wrong shade. Sounds like a detail. It is the difference between hand-built and looks hand-built.
Your theme can be exported as a file and read into another account. Build for several clients and after a few projects you have a small library, instead of retyping the color values from the brand guide every time.
Theme editor
Colors, typeface, corners, borders, how the answers sit, whether a progress indicator runs, whether a photo sits behind it all. Everything in the editor, preview next to it. Thirteen themes come ready-made. Save your own and pull it back out for the next client.
Custom HTML
A section of the form you write yourself in HTML and CSS. Pricing table, comparison grid, callout box, an input layout that has to look exactly like that and no other way. The fields you build into it are real: their answers land in the lead like every other one.
Color world, typeface, edge sharpness, arrangement: all interchangeable. Two forms from the same account need not resemble each other, and from the Starter plan on, the "Powered by asksteps" line under the form disappears too.
The theme editor covers by far the largest part. You only need HTML once something is missing that no form element covers.
The appearance belongs to the form, not the account. A team can work for several clients in parallel, each in their own brand design and on their own domain.
Custom fonts have to sit with you or be embedded; a reference to an external font server gets stripped. Your form loads nothing you do not know about. That question comes up in procurement more often than you would think.
The preview shows the same output the visitor gets. What fits there fits on a narrow screen too.
Neither the theme editor nor the HTML section is tied to a higher plan. Some competitors unlock custom HTML only from their business tier.
Not for the theme editor. It is an interface of color pickers, sliders and dropdowns, and the preview beside it shows every change immediately. You only need HTML once you want to build a section that does not exist as a form element.
The theme applies to the whole funnel or form: questions, answers, buttons, progress. Individual questions may deviate. A question with eight answers often works better as a grid while the rest stay a list.
No, and that is deliberate. Your form runs embedded on other people's pages. Scriptable third-party HTML would be a permanent security hole there, facing every visitor. Where other vendors allow custom JavaScript, they pass that risk on to you.
Yes. Whether you deliver the form through the embed snippet, the WordPress plugin or your own subdomain: it is the same widget with the same theme.
A theme is a stored record, not a state of the interface. Fields you leave empty inherit their values. That is why a form you create today still looks the way you set it after a later extension.
Create a free account and set the first theme. Takes less time than reading this page.
Create an account nowCancel without signing in — with confirmation of receipt.