Stop building forms. Tell Master Joho what you need.
inputdojo is the anti-form. You describe what you're collecting in one sentence. Master Joho builds the form, then asks your people one question at a time. Never a wall of fields.
“salon bookings”
Master Joho built 6 questions:
- Full name
- Phone number
- Which service?
- Preferred date
- Preferred time
- Anything I should know?
Which service?
Just tell me what you're collecting, a sentence is enough, and I'll put the form together for you.
A form builder hands you a blank grid. inputdojo hands you Master Joho.
Form builders make you the form architect, then show your respondents every question at once. inputdojo flips both halves.
The form-builder way
A wall of fields is a wall. People see the scroll bar, guess how long it'll take, and close the tab.
The inputdojo way
One question fills the screen. It reads like a conversation, so people actually finish, and Master Joho built it from a single sentence.
Two shapes of the same job, the grid you assemble, and the conversation Joho builds. inputdojo is one product in the manymoats portfolio.
Describe it. Build it. Collect it.
Say it in a sentence
“Bookings for my salon.” “RSVPs for the launch party.” “Podcast guest pitches.” Plain words, no field types, no drag-and-drop.
Master Joho builds the intake
He builds the right questions in the right order, each one a small, honest field that wears its shape. You add, cut, or reorder. No blank canvas, ever.
They answer, one at a time
Your people get a calm, conversational intake, one question filling the screen, so more of them finish. You get clean answers back.
An answer isn’t a row in a spreadsheet. It’s a person.
Most forms drop every response into a sheet and wish you luck. inputdojo reads each answer, works out what it’s for, sends it where it belongs, and hands you a person you can act on · before you even open it.
It comes in
Maria fills your intake in her own words, one question at a time.
“Maria Lopez · wants color · Saturday morning · first time, a little nervous”It gets read
Not just stored, understood. The point of it and the details are pulled out.
It goes somewhere
No pile to dig through, it lands in the right lane, in front of the right person.
New requests → Sarah (color)It becomes someone
This is a sample of the flow. In the hosted product, rolling out as part of manymoats, real submissions run this automatically; the reading and routing are yours to shape.
and that record is the card waiting for you on the board.
A form ends at “submitted.” inputdojo keeps going.
Most tools hand you a pile of responses and wish you luck. inputdojo turns every answer into a card on a board, so you always know the one thing to handle next · not a spreadsheet to wade through. Same intake, four common jobs. Move a card and watch it flow.
The red card is your next move. inputdojo watches the board and surfaces the one that’s waited longest, so nothing quietly slips through the cracks.
This is a demo board with example responses. In the hosted product, rolling out as part of manymoats, real submissions land in the first lane automatically, and you shape the lanes, rules, and card widgets to fit your work.
Small on the surface. Serious underneath.
Long forms, response caps, and why one question at a time wins.
The real questions people ask when a long form, or a surprise response limit, sends them looking for something calmer. Straight answers about how inputdojo works. No spin.
What's the difference between a form builder and inputdojo?
Why do long forms get so many drop-offs?
What's a response cap, and does inputdojo have one?
Do I have to assemble the one-question-at-a-time flow myself?
What makes an intake "conversational"?
Do I have to know which fields to add?
How much does inputdojo cost?
Is inputdojo just another form builder?
Describe what you need. Watch Master Joho build it.
What you see above is the real thing, running in your browser right now, no sign-up, nothing saved. Type your own intake and see it built.
