Why We Built Cubbies: The Missing Layer Between Forms and Workflows

Three months ago I watched a consultant export 47 Typeform submissions to a spreadsheet, then copy each row into HubSpot Free, then set a reminder in Google Calendar. That's four tools for one lead. Four browser tabs. Four chances for a name to be misspelled or a phone number to disappear between cells.

She wasn't doing anything wrong. She was doing exactly what every form tool on the market assumes you'll do — take your data somewhere else to actually use it. Because every form builder treats the submission as the finish line. Hit submit, done, here's your CSV.

But submissions aren't the product. Workflows are. And the gap between "someone filled out your form" and "you actually followed up" is where most small businesses lose leads, miss tickets, and forget RSVPs.

That gap is why we built Cubbies.

The Problem

Every small business we talked to before building Instaform described some version of the same pain: collecting data is easy, doing something with it is hard.

A wedding photographer uses a Google Form for booking inquiries. She gets ten to fifteen submissions a week during peak season. Each one needs a response within 24 hours — couples move fast and book whoever replies first. But her form responses live in a spreadsheet. Her follow-up tasks live in her head. Her calendar lives in a separate app. By the time she copies a client's details into her calendar and drafts a reply, an hour has passed. Multiply that by fifteen leads a week and her Sunday evenings disappear.

A personal trainer collects intake forms from new clients. Name, fitness goals, injuries, availability. Great — now he needs to create a training plan, schedule the first session, and send a welcome email. The form captured the data. Everything else is manual.

An event planner running weekend workshops gets RSVPs through an embedded form. She has to manually count registrations, check them against a capacity limit, send confirmations, then send reminders the day before. When someone cancels, she has to manually update her count and check the waitlist.

The pattern is always the same: collect → export → reformat → use somewhere else → hope nothing falls through the cracks. The form builder did its job in step one. Steps two through five are on you.

The Insight

We realized that form submissions don't need a better export function. They need a workspace.

Think about email. You don't download your emails into a spreadsheet and then manage them from there. You have an inbox with folders, labels, snooze, archive, and reply. The workspace understands the shape of the work.

Form submissions should work the same way. A lead isn't a spreadsheet row — it's a deal that moves through stages. A support request isn't a database entry — it's a ticket that needs to be triaged, assigned, and resolved. An RSVP isn't a data point — it's a calendar event that needs confirmation and follow-up.

The insight was simple: if we know what kind of form someone is building, we know what workspace they need for the results. A contact form needs a CRM. A help request form needs a ticket queue. A registration form needs a calendar. A survey needs analytics.

Existing form builders couldn't solve this even if they wanted to. Their data model treats every submission identically — a flat row in a table. To give submissions context, you'd need to rebuild the entire architecture. That's exactly what we did.

The Cubby Types

When you create a form in Instaform, you pick a cubby type. That one choice changes everything about how your submissions are displayed and managed.

CRM Cubby turns your form into a sales pipeline. Submissions become deals on a Kanban board. You can drag leads between stages — new, contacted, qualified, proposal sent, won, lost. Each submission automatically creates a contact record. You can add notes, set follow-up reminders, and track the entire journey from first form fill to closed deal. No HubSpot needed.

Support Cubby turns your form into a help desk. Submissions become tickets organized by status and priority. You get a Kanban view where tickets move from open to in-progress to resolved. You can assign tickets, add internal notes, and track response times. It replaces tools like Zendesk or Freshdesk for small teams that don't need enterprise complexity.

Survey Cubby turns your form into an analytics dashboard. Submissions are automatically aggregated into charts — bar charts for multiple choice, NPS score breakdowns, satisfaction trends over time, response rate tracking. Instead of exporting to a spreadsheet and building pivot tables, you get insights the moment responses come in.

Registration Cubby turns your form into an event management tool. Submissions appear on a calendar view organized by event date. You can see capacity at a glance, track confirmed vs. pending registrations, and manage your attendee list. Perfect for workshops, classes, or any event that needs RSVP tracking.

Link Page Cubby connects your form to a link-in-bio page. When someone visits your Instaform link page and fills out an embedded form, their submission appears with context about where they came from and what they clicked. It bridges the gap between your social media presence and your lead pipeline.

Each cubby also has five view types you can switch between: Table for sortable data, Kanban for status columns, Analytics for charts, Calendar for timeline views, and Gallery for visual content. Different cubbies enable different views based on what makes sense for the workflow.

How It Works

Setting up a cubby takes about thirty seconds. When you create a new form, you pick one of the five cubby types from a visual selector. That's it. Your form works exactly the same — you still drag and drop fields, set up conditional logic, customize the theme, and share the link.

The difference shows up the moment your first submission arrives. Instead of landing in a flat table, it appears in the workspace that matches your workflow. A CRM submission shows up as a new deal card. A support submission creates a ticket. A registration appears on your calendar.

You don't need to configure pipelines, create ticket categories, or set up calendar integrations. The cubby comes pre-configured with smart defaults based on the workflow type. If you want to customize — rename Kanban columns, adjust analytics groupings, or change calendar views — you can. But you don't have to.

Every cubby includes the same core views: a sortable, filterable table is always available. But the default view and the available extras change based on your cubby type. CRM cubbies default to Kanban. Survey cubbies default to Analytics. Registration cubbies default to Calendar. It's opinionated where it should be, flexible where it needs to be.

What's Next

We're currently working on two additions to the cubby system. First, automation rules — the ability to trigger actions when submissions meet certain conditions. For example, automatically moving a deal to "qualified" when the submission includes a budget above a threshold, or sending a confirmation email when someone registers for an event.

Second, we're building cross-cubby views. If you run multiple forms with CRM cubbies, you'll be able to see all your deals in a single unified pipeline. Same for support tickets across multiple intake forms.

Cubbies started as a way to give submissions a home. They're becoming the operating system for small business workflows.