Design it by describing it

Counters, buttons, alerts, jobs and cards are designed in a chat - describe it, see a preview from your real data, say yes.

You don't fill in settings screens to build things in Countdat. You describe what you want, and it's designed with you in a chat.

#What you can design this way

  • Counters - what a row is, and its fields.
  • Buttons - actions on rows.
  • Alerts - "tell me when..." rules.
  • Jobs - what to read from your database, and when.
  • Cards - how a counter's rows are shown.

#How it goes

  1. Describe it. "Count deliveries at the front desk, with who it's for and the carrier."
  2. See a preview made from your real data. Not a mock-up - the result on actual rows, where there are any.
  3. Adjust in words. "Make carrier optional." The preview updates.
  4. Say yes. Nothing is saved until you do.

Changes to an existing counter - a new field, a renamed field - are previewed the same way before they're saved. Rows already recorded are kept as they were.

Still stuck? Write to us and a person will reply.
Email support

Updated 2026-10-09