stepbase

By job

One link, every request type, no accounts

A form collects a request. It doesn't assign an owner, chase a reply, or say whose turn it is. A portal gives people one branded place to ask, and turns every submission into tracked work with a name against it.

The form was never the hard part

Most teams solve intake in an afternoon: a form, a link, a spreadsheet behind it. The problems start on submission two hundred. Nobody owns a row. Status lives in whoever remembers. The requester emails to ask where their thing is, and answering means scrolling. The form captured the request perfectly and did nothing with it.

Today

  • A shared form drops rows into a spreadsheet nobody owns
  • Work is assigned by whoever spots it first, or in a group chat
  • Status is a colour on a cell, updated when someone remembers
  • Requesters chase by email because there's nothing to link them to
  • Half-finished requests go quiet with no one accountable
  • "How long does this usually take?" has no answer

On stepbase

  • A public link anyone can submit through: no account, no login
  • Every submission opens a tracked instance with a named owner
  • Requests route themselves on what was submitted, not who reads it first
  • Anyone in the workspace can see where a request sits without asking its owner
  • Nothing sits unowned: each stage has someone responsible
  • Every step is timestamped, so cycle time is a fact rather than a guess

How it works

Publish

Publish the portal

One branded page listing every request type you accept, on a link anyone can open. Clients, other departments and the public submit without an account, and a form you publish next week appears on it automatically.

Request a project
Public link

No account needed. Anyone with the link can submit.

Name
Request type
Budget
Details
Route

Route on what came in

Branch on the submission itself. Video work to the editors, brand work to design, anything over budget to a lead first.

Submission
Video edit
$1,800
Route on type
Video → Editors
Brand → Design
> $1k → Lead
Editors
Video work
Design
Brand work
Team lead
Over budget
Assign

Give it an owner

Each stage lands with a person, a team, or a role. Team-assigned work is claimed, and the claim is recorded, so there's always an answer to who did this.

Design team queue
MK
JD
AR
3
Brand kit #218
Review task · Design
Unassigned
Track

Track it to done

The request moves through its stages with every action timestamped, so status is something you read off the request rather than something you ask three people about.

Brand refresh #218
Request status
Waiting
Submitted
Routed
In review
Done

FAQ

Common questions

No. Intake forms are shared as a public link and can be submitted anonymously, or gated behind an email address if you want submissions tied to a person.
A form ends at submission. Here the submission is the start: it opens a tracked request, routes on what was filled in, assigns an owner, and records every step through to completion.
Yes. One form can feed many paths: conditions branch on the answers, so a simple request can close in one step while a large one picks up an approval on the way.
Yes. Every submission is its own tracked request showing the current stage, who holds it, and everything that has happened so far, so answering a chaser takes one click instead of a thread.
Point the new form at the same audience and run it alongside your sheet. Existing rows stay where they are, and there's no import step before you can start.

What process would you turn into an app?

Build it free, or start from a template and change what you like. No credit card, no setup fees.

Start from a template