By industry
Custom furniture website: where requests stall
A buyer has a room in mind and a photo, but not a wood name or a budget. Mimiq sends simulated visitors through your request form and shows the field where each one gave up.
Why does a custom furniture website get few commission requests?
Commission requests stall when the form asks for a spec the buyer has not decided yet. Visitors usually arrive knowing the room, not the spec. They do not know the wood name, the unit your form expects, or what a fair budget is, so a form that requires those answers stops them before they write anything. A simulated test sends a visitor through your request form on a phone, with a made-up room and a vague idea, and shows the field where the visitor could not continue.
What this looks like in a report
“I know it has to seat eight. The box wants centimeters and I only have meters. What do I type for two meters, 2 or 200? I do not know the wood names either, so I will look somewhere else.”
The fix. Give the dimensions fields a unit selector with meters and centimeters, and accept a decimal number. Add not sure yet to the wood list, make the budget optional, then send a new simulated visitor with a room size and no wood choice and check whether the form submits.
An illustration. Run a test to see your own.See a real sample report
Request forms ask a buyer for a spec they have not decided yet
A custom piece starts as a feeling about a room. The buyer knows they want a dining table for eight in something warm, and they have one photo from a magazine. Your form wants a width in centimeters, a species from a dropdown, a finish, a budget and a delivery date. Each field is reasonable from the workshop, and each is a guess from the sofa. A visitor who types 2 meters into a field that expects centimeters gets an error that does not say which unit it wants. A visitor who enters 0 in the budget because they have no idea gets stuck.
- Can a buyer submit a request with the wood marked as not sure yet?
- Does the dimensions field name its unit, and accept a decimal number?
- Is the budget field optional, or does it reject an answer such as not sure?
- Does the form say what happens after submit, and where the maker's reply will come from?
- Does the request still go through when the room photo is left out?
The request form asks for the spec before the buyer has one
A buyer of a one-off piece starts somewhere else than a shopper. They describe a room, a use and a feeling, and only later turn that into numbers. Many forms expect the numbers first. A dimensions box with one unit, a wood list with a handful of species and no way to say unsure, and a budget that will not take zero are three separate stops. Each looks like a small detail to a maker who knows what a board is. On a phone, to a buyer who has never ordered a table, they look like homework, and the request stops halfway.
The order matters too. If the photo upload comes after the budget, a buyer with a picture of the room may give up before they reach it. If the form asks for a delivery date before it has said how a commission works, the buyer cannot tell whether the maker can start in time. A form that asks questions in the order a buyer can answer them keeps them in it.
Wrong and right versions of the same three fields
Wrong: a single box labeled width in centimeters, with a red error when the visitor types 2 m. Right: a number box and a unit selector next to it, with the unit shown in the message when a value is rejected. Wrong: a wood dropdown that starts with oak, walnut and ash, with no other choice. Right: the same list, plus not sure yet. Wrong: a required budget with a minimum that a single chair would not reach. Right: an optional budget with a range the buyer can change later. Each right version keeps the buyer typing, and each wrong version makes them guess a number they do not have.
The walnut table request to send through first
Send one simulated visitor to your commission form with this task: request a walnut dining table for eight, budget not decided yet. The visitor is a homeowner with a room in mind and no wood, size or budget chosen. Give it a made-up room size, and let it leave the wood as not sure wherever the form allows that. The report shows the field where it stopped, with a screenshot of that step.
Four ways to find where a request form stops
| Method | What it shows | What it misses |
|---|---|---|
| Filling in the form yourself | Fields you already know the answer to | Questions that only a buyer without your background finds unclear |
| Watching real visitors in a session replay tool | Where real buyers hesitate, on your traffic | A buyer who never reaches the form, and why they left |
| Asking friends to request a commission | Whether the wording makes sense to someone you know | Whether a stranger with no link to you would wait it out |
| Simulated visitors through the form | Fields a stranger could not get past, and the message they saw | Rates, and whether a real buyer would have commissioned anything |
What you get with Mimiq
- 01
Run it by hand, or on every pull request
Paste a link and a task in the app and watch the visitors work. Or run them on every preview deploy: the GitHub Action comments on the pull request, any other CI can call the MCP endpoint, and your coding agent can run it too.
- 02
Bugs and usability problems in one report
The browser records errors and failed or slow requests on the step they happened. The visitors say where the wording or the steps confused them, and where they left.
- 03
Visitors that behave like your audience
Each visitor is a different profile with a reason to be there, matched to who the page is for, described by you, or built from your own customers.
- 04
A prompt to fix each problem
Every problem comes with a fix to paste into Cursor, Claude Code, Lovable or any coding agent, and one prompt hands over the top problems at once. Then send the same visitors through again.
- 05
Follow every visitor
See each visitor's whole path, step by step with screenshots, and what it was thinking at every step. Ask any visitor a question.
The browser records relevant JavaScript errors and failed or slow app requests encountered during the run, attached to the step where they occurred. The visitors are simulated: they find problems, they do not predict how many real people will convert.
A new wood or finish option can bring a required field back
The first run finds the field. The fix changes it: a unit selector, a not sure option, a budget that can stay empty. Run the same request again after each change, and after you add a material or a finish. Test it again before you send traffic from a search or a Pinterest board, since those visitors bring their own room and their own questions.
Starter
Try it on one launch
About 4 tests of 5 visitors
- Visitors on your landing page, signup and checkout
- Where they left and why, with a fix to copy for each problem
- Run it in the app or on every pull request
- Ask any visitor a question, included
- Test accounts and protected previews
Builder
Test every build
About 20 tests of 5 visitors
- Everything in Starter
- Credits refill each month, and what is left rolls over once
- Cancel anytime
Pro
Test every release, as a team
About 60 tests of 5 visitors
- Everything in Starter
- Credits refill each month, and what is left rolls over once
- Cancel anytime
Scale
Test at scale, every day
About 240 tests of 5 visitors
- Everything in Starter
- Credits refill each month, and what is left rolls over once
- Priority support
- Cancel anytime
Questions
Will the test tell me how many buyers will request a commission?
No. Mimiq does not predict how many buyers will request a commission, and it cannot give you a rate. It shows the field where a simulated visitor stopped and the message it saw. Rates come from your analytics, or from a change you measure on the same kind of traffic over time.
Can a visitor pay a deposit on a commission?
No. A deposit that needs a real card ends the test at the payment step, and the report shows that step. Use made-up details everywhere else, and do not type a real client's name, address or card number into a test.
Does the test check my wood names, finishes and lead times?
No. The test checks whether a visitor can get through the form and understand each field. It does not check whether your wood names, finishes or lead times are correct, or whether your terms are fair. Your workshop records and real customers answer those questions.
What if my form uses inches and my visitors are in Europe?
The test shows what happens when a visitor enters a unit your form does not expect. Run it once with metric and once with imperial, and see which one the form rejects. The fix is to show the unit beside the field, or to accept both, so a buyer's number is not thrown out.
Keep reading
Send visitors and see what breaks first.
Your first test is free: sign in with Google and it starts right away. Last checked 2026-11-02.