Collect survey responses in 10 minutes — no spreadsheet wrangling

Every team eventually needs answers from real people — how did the workshop go, which roast should we stock, what should we build next. And most of the time the "survey stack" ends up as a third-party form tool, a spreadsheet export, and a pile of copy-paste to make the answers usable.

On Aglyn the whole loop — model, form, responses, analysis — lives in one place. Here is the actual flow, end to end.

1. Model the data first

Start on the Data page and create a dataset. Give it typed fields that match the questions you actually want answered:

• satisfaction — a star rating
• visit — radio choices like First time, Monthly, Weekly
• topics — checkboxes for the areas they care about
• comments — a multiline text field for everything else

Two things make this better than a spreadsheet. First, every field has a type, so a star rating can never arrive as the string "five". Second, each field has a stable reference ID separate from its display label — rename "How satisfied are you?" to anything you like later, and every response, binding, and form mapping keeps working.

2. Design the form where your visitors are

Open the screen in the besigner — Aglyn's visual builder — and drop in a Form from the element picker. Add a Form Field per question and pick the matching input type: the star-rating field renders stars, radio choices render as radios, checkboxes as checkboxes.

Then point the form at your dataset with Write to dataset. Field mapping is by reference ID, so the wiring is rename-safe. Set the submit label and a success message, and style the whole thing with your site theme — it is a normal element on a normal page, not an iframe embed.

3. Publish and watch responses arrive

Hit Publish. The survey is live at your URL, on your domain, in your design.

Responses land in the dataset table in real time. From the Data page you can:

• Filter and sort — show only weekly visitors who rated under three stars
• Export — one click to CSV or JSON
• Chart it — bind a repeatable component to the dataset and visualize answers on an internal dashboard page

Validation runs on the way in, on the server, against the same typed model — so the table never fills up with junk rows.

Why this beats the form-tool stack

• No context switching. The survey is a page on your site, edited with the same builder as everything else.
• No export-import loop. Responses are already structured data you can query, chart, and act on.
• No breakage on rename. Labels are display-only; the data contract is the reference ID.

From blank page to live survey with structured responses: about ten minutes. The longest step is deciding what to ask.