Once you complete the questionnaire, Hey Button advances you through three sequential stages: Stitch, Press, and Mend. Stitch converts your answer into a teammate configured around how work genuinely reaches your business. Press establishes explicit approval rules and tests the teammate on real examples before any customer encounters it, while Mend keeps the setup tuned after launch.
What does the questionnaire request first?
The questionnaire opens with a single question: what would you take off your plate first? Answer in your own words, avoiding technical language. Describe the recurring task that consumes the most attention, even if it appears small from the outside, since a small answer is entirely enough to begin.
Sample answers, for illustration only:
- A lawn care owner might write, "Every morning I retype the same quote details from texts and emails."
- A cleaning business might write, "Rescheduling requests pile up in the inbox and nobody owns them."
- A small law office might write, "New client forms arrive without the documents we need to open a file."
Write your answer the way you would explain the work to an incoming colleague, and skip internal shorthand that only your team recognizes. Plain, unpolished detail gives the next stage its strongest raw material.
The answer binds you to nothing. Hey Button utilizes it to determine what to explore next, which keeps the conversation from drifting toward a generic template that ignores how your business genuinely operates. In effect, it gives the conversation a concrete starting point instead of a blank page.
What happens during Stitch?
Stitch is the intake stage, a structured and deliberately unhurried conversation about how work reaches your business and where it stalls. The same conversation examines which tools your team already relies on and where invisible busywork accumulates week after week. Expect questions specific to your operation, because generic questions produce generic plans that fit nobody well.
The questions vary by business type, since inboxes and paperwork differ considerably from one trade to the next. A lawn care company may need to sort quote requests, schedule changes, and invoice reminders, while a contractor's paperwork typically centers on estimates, change orders, and permit timelines. A cleaning business frequently juggles recurring bookings, one-time jobs, and reschedules, and a small law office manages intake forms, document requests, and deadlines. Stitch begins with those particulars rather than with a template.
By the end of Stitch, the goal is a clear map that demonstrates which requests arrive, from where, what a good response looks like, and which steps need your sign-off. That map forms the basis for the rules you define in Press.
Stitch also scrutinizes the questionnaire answer. If the description sounds like one task but the real work is genuinely three, the conversation separates them, and each workflow receives its own rules later. Separating them early keeps the setup clean.
How are integrations checked before anyone makes promises?
Integrations are verified during Stitch, before any promise is made about what a teammate can connect to. That sequence is deliberate. A proposal written earlier would describe capabilities nobody had confirmed, and you would have no practical way to detect the gap until something failed during real work.
List every tool you utilize, including the ones you rarely open. An outdated scheduling tool or a shared inbox nobody verifies can change which workflow is realistic. Candid answers here prevent rework later, because connections and rules become harder to change after go-live.
Not every workflow needs a full connection. Some tasks work well from a shared document or a forwarded email, and a teammate can handle those without a deeper link. Determining which path fits is part of the Stitch conversation.
The trade-off is time. Verification takes longer than a quick yes, and a business that wants results this week may find that frustrating. The alternative, however, is a promise that breaks in production, which costs considerably more time and trust.
What changes at go-live in Press?
Press is the go-live stage. Before any work reaches a customer, you and Hey Button agree on three boundaries: what the teammate may read, what it may draft, and what it may do alone. Those boundaries become the reference point for every later decision about its responsibilities.
The principle behind Press is straightforward: start small and demonstrate that the system works. One defined workflow operates first. You observe the teammate handling real examples, and only then does a broader responsibility arrive, so early errors remain contained and straightforward to correct.
Consider an illustrative sequence for a cleaning business. The first workflow sorts incoming booking requests and drafts replies. The teammate can read requests and draft responses, but it does not confirm bookings or change a schedule until you approve that rule, which you do once you have reviewed enough real examples to trust the drafts.
A narrow task with clear answers can move through Press rapidly. Work with many edge cases needs a longer review, and that additional time is part of the setup rather than a delay to route around.
Who approves what the teammate does?
You do. Customer messages, spending, and sensitive changes remain behind the approval rules you establish during Press, so those decisions never happen silently. The teammate can prepare a reply, sort an inbox, or draft a follow-up list for your review, while the approval rules determine which steps proceed without you. Drafts wait for your approval before anything moves forward.
Hey Button is direct about the limits of the technology: AI can make mistakes. Review and clear limits are part of the setup, not an afterthought or a liability footnote, and that is precisely why the approval step exists. Months of strong results can justify revisiting a rule, but review of customer-facing work should remain in place.
Illustrative example, not a real case: a lawn care company receives the message, "Can you give me a quote for a spring cleanup?" The teammate organizes the inquiry, notes that the address and photos are still missing, and drafts a reply for approval. Nothing is sent until you approve it.
How do read-only, draft-and-approve, and full access differ?
Access is set per task rather than through one global switch. Hey Button utilizes three levels, and each workflow receives the narrowest level that accomplishes the job.
| Access level | What the teammate can do | Common starting point |
|---|---|---|
| Read-only | Look at information and report on it | Sorting an inbox or summarizing open requests |
| Draft-and-approve | Prepare replies or changes that wait for your sign-off | Customer replies, quote drafts, follow-up lists |
| Full access | Complete defined actions within the rules you set | Routine, low-risk steps already proven in Press |
Full access is not the objective for every workflow. A law office may keep a draft that waits for attorney review as its permanent setting, because the review itself is the point. A contractor's routine scheduling message may move to full access once Press demonstrates the rule holds. Spending and sensitive changes are where most owners keep a human step.
Access also demands ongoing attention. Lower the level when a rule proves too loose, and raise it only with evidence drawn from real examples.
What happens after launch in Mend?
Mend is the ongoing stage. It keeps the configuration current as your business changes, covers connected services, and keeps model routing. People make the changes. When prices, staffing, or tools shift, the rules are updated through that process, and the teammate never rewrites its own instructions.
Hey Button operates on OpenClaw, an open automation framework. Hermes is part of the underlying runtime, and models such as Claude and GPT respond through it depending on the task. Hey Button does not utilize a proprietary model built from scratch. Each job routes to the least expensive model that still performs it correctly, and if the first-choice model is slow or unavailable, the work can fall back to another capable model.
A model switch never alters your teammate's instructions, business facts, or access boundaries. That separation is deliberate. You can review the rules once, rather than re-verifying them each time a different model answers.
The client portal is where you see the results of that work, described in plain language. It demonstrates what your teammate did and why. When something looks wrong, you can trace the reasoning instead of guessing at causes, then determine whether a rule needs to change. Mend makes that review routine.
How is pricing handled before you commit?
Pricing is provided in writing before you commit to anything. Setup and ongoing support are quoted around your specific workflows and integrations, so the figure reflects the work you genuinely need. Software subscriptions and usage charges are identified before you commit. Hey Button's pricing page promises no surprise line items, and the proposal itemizes each cost. You can review how pricing is structured before you determine.
Read the figures alongside the approval rules, because cost and scope shape each other. A broader workflow can change the usage picture, so a quote that looks reasonable for one narrow task may warrant a second look once additional work is added.
The questionnaire carries no commitment. Its purpose is to describe your work clearly enough to support an accurate, reviewable proposal.
Who will you genuinely talk with?
You talk directly with the founder, Lucas M. Button. The conversation continues from the first exchange through launch and beyond, rather than passing to a rotating group of unfamiliar staff. One person shapes your rules, answers your questions, and remembers why each rule exists.
For a small business in Fort Wayne or anywhere in Northeast Indiana, a founder-led conversation keeps the reasoning behind each rule in one place. The trade-off is focus. A founder-led process gives each conversation close attention, so come prepared with complete answers to every session.
What should you bring to the questionnaire?
Bring four things: the tools you utilize, the channels where requests arrive, the step where work typically stalls, and who signs off on what today.
- Tools you utilize every day, every week, or rarely
- Where requests come in, such as email, forms, a shared inbox, or text messages
- The point where work waits longest
- Who approves messages, quotes, and spending right now
Include the names of tools you rarely open. They shape the integration verify, and a forgotten tool can alter which workflow is realistic.
Thorough answers take longer to write. A shorter answer still works, but expect more follow-up questions in Stitch. If you have no defined recurring task yet, describe the problem you feel instead, such as work that never gets finished. Stitch can work backward from a symptom to the task behind it.
To see the full sequence first, read how Hey Button works. Then answer the questionnaire while the details remain fresh.
Frequently Asked Questions
Is the questionnaire a commitment? No — The questionnaire describes your work so a reviewable proposal can be written. Pricing and scope come in writing before you commit to anything, so you determine after reading them. Filling it out does not sign you up for setup or ongoing support.
What if I cannot describe my workflow clearly? Typically that is fine. Write the task the way you would explain it to a new colleague, and list the tools you already utilize. Stitch requests follow-up questions to fill the gaps, so a rough first answer still gives the conversation something concrete to build on.
Do I have to grant access to every tool I list? No — Access is chosen per task, across read-only, draft-and-approve, and full access. Start with the narrowest level that covers the workflow. Widen it only after the teammate handles real examples well and you have reviewed the results in Press.
Can the teammate message customers without my approval? Typically not at launch. Customer messages stay behind the approval rules you set during Press. A narrow, low-risk message type can go out alone only after you write that permission into a rule, and the teammate never widens its own permissions silently.
Do I need technical skills to answer the questionnaire? No — The questionnaire is written in plain language, and the answers should avoid internal jargon. Describe the work as you would to an incoming colleague. The follow-up conversation in Stitch handles the technical details, including checking how your tools connect.
Ready to begin? Start the Hey Button questionnaire and tell us what you would take off your plate first.
Frequently Asked Questions
- Is the questionnaire a commitment?
- No — The questionnaire describes your work so a reviewable proposal can be written. Pricing and scope come in writing before you commit to anything, so you determine after reading them. Filling it out does not sign you up for setup or ongoing support.
- What if I cannot describe my workflow clearly?
- Typically that is fine. Write the task the way you would explain it to a new colleague, and list the tools you already utilize. Stitch requests follow-up questions to fill the gaps, so a rough first answer still gives the conversation something concrete to build on.
- Do I have to grant access to every tool I list?
- No — Access is chosen per task, across read-only, draft-and-approve, and full access. Start with the narrowest level that covers the workflow. Widen it only after the teammate handles real examples well and you have reviewed the results in Press.
- Can the teammate message customers without my approval?
- Typically not at launch. Customer messages stay behind the approval rules you set during Press. A narrow, low-risk message type can go out alone only after you write that permission into a rule, and the teammate never widens its own permissions silently.
- Do I need technical skills to answer the questionnaire?
- No — The questionnaire is written in plain language, and the answers should avoid internal jargon. Describe the work as you would to an incoming colleague. The follow-up conversation in Stitch handles the technical details, including checking how your tools connect.
Hey Button
Want a teammate that handles this for you?
Answer a few questions about your business and Hey Button will show you what an AI teammate would take off your plate, with you approving anything that goes out.
