--- title: "Instaform's First Week: Building in Public Retrospective" slug: first-week-building-in-public description: "Here's what happened in the first seven days after we opened Instaform to waitlist members. Real numbers, honest lessons, and what we're fixing next." publishedAt: "2026-03-31" author: "Instaform Team" tags: ["building-in-public", "startup", "retrospective"] locale: en --- Here's what happened in the first seven days after we opened Instaform to waitlist members. We're sharing this because we believe in building in public. Not the curated version where every metric goes up and to the right, but the real version — what worked, what broke, and what surprised us. If you're thinking about launching your own product, maybe our stumbles will save you a few. This is week one. Everything that follows is honest. ## Launch Day We sent the first batch of invites on a Tuesday morning. We'd been debating whether to launch on a Monday ("people are in work mode, they'll try new tools") or a Thursday ("less pressure, people browse more before the weekend"). We picked Tuesday as the compromise. In retrospect, the day didn't matter nearly as much as we thought. The invite email went to our first 200 waitlist members. Subject line: "Your Instaform account is ready." Simple. No hype. The email explained what Instaform does in three sentences, had a single "Open your dashboard" button, and included a line saying "reply to this email with any feedback — it goes straight to the founder." Open rate: 68%. That's high, but this was a waitlist — these people had signed up specifically to get early access. Click-through rate: 41%. So out of 200 emails, about 82 people clicked through to the dashboard. The first signup happened eleven minutes after the email went out. The first form was created fourteen minutes later. The first support email arrived twenty-three minutes in — someone couldn't figure out how to add a file upload field. (We fixed the UX within the hour.) By end of day one, we had 74 accounts created, 31 forms built, and 8 forms that had been published with a public link. We also had 12 reply-to-this-email messages, ranging from "this is exactly what I needed" to "where's the Zapier integration?" We didn't sleep much. ## Week 1 Numbers Here's where we landed after seven days: - **Waitlist invites sent:** 200 - **Accounts created:** 127 (63% activation from invite) - **Forms created:** 89 - **Forms published:** 34 (38% of created forms went live) - **Total submissions received:** 247 (across all published forms) - **Link pages created:** 19 - **CRM cubbies active:** 11 - **Support cubbies active:** 4 - **Survey cubbies active:** 7 The number we cared about most: 34 forms published. Creating a form is curiosity. Publishing it means someone trusted the tool enough to share it with their audience. That's 27% of all accounts — better than the 15% we'd internally predicted. The number that worried us: 247 submissions across 34 forms. That's an average of 7.3 submissions per form in a week. Some forms had zero submissions (just published but not yet shared). Three forms had over 40 submissions each — those were the ones embedded on active websites. The gap between "published" and "getting real traffic" was bigger than expected. ## What Surprised Us **Cubby type distribution surprised us.** We expected CRM to dominate. It didn't. Survey cubbies were the second-most popular after standard (no cubby type). People wanted to collect data and see charts immediately. The built-in analytics view — bar charts for multiple choice fields, NPS score breakdowns, satisfaction trends — was the feature people mentioned most in feedback. We'd spent weeks building the CRM Kanban view, and the analytics charts we'd shipped as an afterthought were the hit. **Link pages found their audience fast.** We expected link pages to be a secondary feature, something people discovered after building forms. Instead, 19 of 127 accounts created a link page in their first session. Several created the link page *before* creating a form. One user built a full link-in-bio page with social icons, a YouTube embed, and a scheduling link — then added a contact form as the last block. The link page was their entry point, not the form. **The form builder wasn't the bottleneck — the publishing flow was.** Nobody complained about dragging and dropping fields, setting up conditional logic, or customizing themes. What tripped people up was the gap between "my form looks good in the editor" and "it's live on my website." The embed options (iframe, script, popup) confused some users. One person emailed asking "how do I just get a link I can share?" The direct link was there, but it was buried in the share menu. We moved it to a prominent button within 48 hours. **Spanish-speaking users arrived faster than expected.** Our waitlist was international from the start, but we didn't expect so many early users from Latin America. Within the first week, 23% of accounts were set to Spanish locale. Our Spanish translations were solid (we'd shipped them from day one), but some form template names felt unnatural in context. We're still polishing. ## What We're Fixing Next Based on week one feedback, here's what we're prioritizing: **The publishing flow.** We're simplifying the path from "form is done" to "form is live." The share button will be more prominent. The embed code page will show a preview of what the embedded form looks like. And we're adding a "copy link" button that's impossible to miss. **Form templates for specific use cases.** Several users said they wanted to start with a pre-built form and customize it rather than building from scratch. We have templates, but the gallery needed better categorization and preview. We're adding use-case categories (lead gen, feedback, support, registration, survey) and a one-click "use this template" flow. **Notification customization.** Right now, you get an email when someone submits your form. Users want to customize what's in that email, who receives it, and whether to send an auto-response to the submitter. This was already on the roadmap; user feedback just moved it up. **Mobile form editing.** The form builder is desktop-first. Several users tried to make quick edits from their phone and found the drag-and-drop interface frustrating on a small screen. We're not going to build a full mobile editor, but we're making common operations — editing labels, toggling field visibility, reordering fields — work better on mobile. We're sharing this not because we think our numbers are impressive (they're not — this is week one of a product nobody's heard of) but because we think the building-in-public community needs more honest posts. Your week one will look different from ours. But the pattern — some things work, some things break, the things you obsessed over aren't the things that matter — is probably universal. Week two update coming next Monday. Follow along if you want to see how this goes.