Most platforms describe their build flow with marketing language. We'll just walk through it. Forty-eight hours, idea to live agent, exactly what every step looks like.
Hour 0: the intake conversation with Ace
You start with a conversation. Not a form. Ace — our build agent — asks roughly five questions, in plain English:
- What does your agent do, in one sentence?
- Who specifically is it for?
- What's the user experience — chat, embed, voice, scheduled?
- What systems does it need to talk to?
- What does it absolutely never do?
These are the same questions a senior agent designer would ask. The difference is you're answering them conversationally — Ace clarifies, prompts on vague answers, suggests defaults if you're unsure. About 30–40 minutes for most builders.
Hour 1: agent design
Ace produces the agent design. This isn't a list of prompts — it's a structured proposal: behaviour, voice characteristics, tools and integrations, decision rules, approval gates, and what gets escalated to you. Read it through, ask for changes, repeat.
For most builders this loop happens 2–3 times. By the end you've got an agent that looks specifically like the thing you described, with edges sharpened.
Hour 2–4: voice calibration
The hardest part. Voice is what makes an agent feel "like you" vs "like ChatGPT." You upload sample messages, prior emails, your newsletter, your social posts — anything in your real voice. Ace calibrates against it.
You then review 5–10 sample outputs from the agent and edit them. The agent learns from your edits. Three rounds usually gets you 80% there. The remaining 20% comes from real users in production (covered later).
Hour 5–6: integrations & tools
Connect the systems your agent needs — calendar, CRM, email, Stripe, your ticketing system, whatever fits. Most agents need 1–3 integrations on day one. Squidgy supports every major SaaS via native integration; less common ones via webhooks.
Approval workflow setup happens here too. You configure what requires your sign-off and what the agent can do autonomously. Most builders start conservative (everything requires approval) and loosen as the agent earns trust.
Hour 7–24: testing in sandbox
Squidgy gives you a sandbox where you test the agent end-to-end with fake users you create. Walk through the typical flows. Edge cases. The bad-actor cases (what if a user tries to make the agent do something out of scope?). Fix what breaks.
Most builders find 5–8 issues in this phase. They're usually small voice/scope adjustments, not fundamental rebuilds.
Hour 24: pricing & listing
Set your pricing model. Subscription? Per-use? Hybrid? Decide whether to list publicly in the marketplace, share via private link, embed on your site, or all three. Squidgy handles billing, payouts, and tax automatically.
Hour 25–48: friends-and-family beta
Get 5 real users on the agent — friends, peers, your existing customers, people from your community. Watch the dashboard. See how they actually use it. Fix what surfaces. Voice usually gets dialled in here as you see real interactions.
What to watch for
- Where do users get confused about what the agent does?
- What edge case did you not anticipate?
- What does the agent escalate to you that it should handle?
- What does the agent handle that it should escalate?
- Where does the voice still feel "off"?
Hour 48: live
Public listing in the marketplace, share with your audience, run a soft-launch post. Squidgy handles billing — you get monthly payouts and a real-time dashboard of usage, revenue, and retention.
What "done" looks like
For most Squidgy builders: 48 hours from initial conversation with Ace to first paying customer. The agent isn't finished — it never is — but it's earning. The next 90 days are spent watching it work, adjusting voice and scope based on real usage, and listing it in vertical-specific marketplaces if you choose.
That's the build flow. Honestly. That's how it works.