A little prep before your free consult is the difference between a vague wish list and a build we can start in days. You don't need a spec or a technical document. You need clarity on one task, the materials behind it, and what a correct answer looks like. Here's how to get there in about an hour.

Step 1: Pick the one task that eats the most time

Resist the urge to fix everything at once. The strongest first build is a single, repetitive task that you or your staff do over and over — the one you'd happily never touch again.

Good candidates share a pattern: someone reads an incoming message or form, looks something up, and types back a fairly predictable answer. Think:

  • The same questions, answered all day — pricing ranges, availability, what's in stock, "do you service my area?"
  • Turning a request into a draft — an inbox lead into a quote, a phone note into a follow-up, intake details into a first-draft document.
  • Sorting and routing — deciding which emails are real leads, which are spam, and who each one should go to.

If two tasks feel tied, pick the one with the clearest right answer. AideaMaker builds remove whole tasks, not parts of tasks, and the cleaner the task boundary, the more completely we can take it off your plate. Not sure which to choose? Ada, our free AI Solution Finder, will walk you through it in a few minutes and name a concrete first build.

Step 2: Gather what the AI will need to know

Your AI is configured on your business — your products, your terminology, your prices, your process. That only works if we have the source material. Before the consult, collect the documents that hold the answers:

  • Your price book or rate sheet — the actual numbers your team quotes from.
  • Templates you reuse — quote layouts, proposal boilerplate, standard email replies, intake forms.
  • Reference material — service-area lists, product specs, warranty terms, policies, FAQs.
  • A handful of real examples — three to five past requests and the good answers you actually sent. These teach the assistant your voice and your standards better than any instructions.

A construction firm might bring its estimate templates and material price list; a law office might bring intake questionnaires and standard engagement language. Don't clean these up or format them — bring them as they are. Messy real documents are more useful than a tidy summary.

A note on privacy: you bring your own AI key, so your documents stay yours. They are never pooled with other clients, never resold, never used to train a public model.

Step 3: Note where the work actually lives

The build goes into the tools you already use, not into a separate tab someone has to remember to open. So tell us where the task happens today:

  • The inbox — leads, quote requests, and questions arriving by email.
  • Your CRM or scheduler — where records, deals, and appointments are kept.
  • Website forms — contact, quote, or booking forms that feed you work.
  • Quotes, documents, or spreadsheets — where the output needs to land.

Knowing the start point and the finish point lets us wire the assistant to do the whole loop — read the request where it arrives, produce the answer, and put it where it belongs. How it works covers the build path in more detail.

Step 4: Decide what "good output" looks like

This is the step most people skip, and it's the one that makes your build reliable. For your chosen task, write down what a correct, finished answer includes:

  • What it must always say — required disclaimers, terms, a specific tone.
  • What it must never do — never quote a final number without a site visit, never give legal advice, never promise a date that isn't confirmed.
  • When to hand off to a human — the situations where the assistant should stop and flag you instead of answering.

These become the guardrails that keep answers consistent and in-bounds — the same correct answer every time, not a different improvisation per request. The clearer your "good" and "never," the tighter we can set them.

What to bring to your free consult

Walk in with four things: the one task, the documents and examples behind it, where it lives in your tools, and your definition of good output. That's a complete brief.

If you'd like a sense of the payback before you talk to anyone, the ROI calculator gives a quick estimate from your own numbers. When you're ready, book a free consult — no cost, no obligation, and you'll leave knowing exactly what your first build would do.