About Sedge

By next spring, nobody asks where the response went

Sedge is a form, quiz and application intake builder. It was made for the point after a form is published, when the answers start arriving and someone has to do something with them.

Choose your plan Read the principles Each plan is a one-time purchase.

01 — The problem

Forms were never the hard part

Putting fifteen questions on a page takes an afternoon. What follows takes months: answers scattered across inboxes, one spreadsheet per program, reviewers asking who owns which application, and a completion rate nobody can explain.

The form got built. The part after it was left to email.

Sedge starts from that gap. The builder is there, drag and drop, with branching and scoring. But the product is organised around what happens to a response: tagged on arrival, assigned to a person, sent to the tool that needs it, counted per question.

Applicants get one question at a time. Your team gets one workspace.

02 — Principles

Four rules we check changes against

  1. 01

    Ask less

    Every field has to earn its place. Branching exists so people skip what does not apply to them, and drop-off reporting exists so you can see which question costs you the most.

  2. 02

    Responses are the product

    A submission is not a notification. It carries tags, a stage, a reviewer and a score, and it stays in the workspace where the whole team can read it.

  3. 03

    Fit the tools already open

    Slack, Google Sheets, webhooks, HubSpot, Jira. Sedge sends responses to them instead of asking your team to move somewhere new to read them.

  4. 04

    Pay once, plainly

    Three plans, each a single payment. No renewal date, no per-seat arithmetic. The price on the page is the price.

03 — How it’s run

Built in the open, supported by readers

Sedge ships in small releases and writes down every one in the changelog. Bugs reported to support go to the people who write the fixes, and the answer comes by email from a named teammate, not a ticket number.

Marsh plans add priority support. Every plan gets the same product and the same release notes.

  • ReleasesSmall and frequent, each with a plain-language note in the changelog.
  • SupportEmail only, read by the team that builds the product.
  • DataExports stay available as files, so a response is never locked in.
  • AccessRoles, SSO and audit logs on Marsh for teams that need a paper trail.
  • PricingOne payment per plan. Changes to a plan are announced before they apply.

04 — Where it’s going

Next on the list, in order

The roadmap is short on purpose. Each item below comes from something teams asked support for.

05 — Plans

When the answers come in, be ready

Seedling, Meadow or Marsh. One payment per plan, and the first form takes an afternoon.

Choose your plan