Planning help for businesses that never had an analyst

Describe the problem.Get the best plan.

Solvable turns a problem you describe in plain words into a mathematical model, solves it, and explains the answer. It asks when something is missing, shows every assumption, and lets you change one thing at a time.

Example · Hansen Bakeri

  1. You: I run a bakery with 6 staff. Two shifts a day, 6–14 and 14–22. Sarah can't do mornings, and nobody should work more than 5 shifts a week.
  2. Agent: How many people do you need on each shift?
  3. You: Two and two on weekdays. Saturday needs three in the morning, Sunday evening just one.
  4. Agent: builds a model with one rule per requirement, solves it, and shows a week's schedule where everyone gets five shifts.
  5. You: Leo has Saturdays off from now on.
  6. Agent: adds that one rule, re-solves, and moves six shifts across three people.

How it works

From a few sentences to a plan you can check.

Before: the whiteboard in the back room.
  1. 01 · Problem

    You describe it the way you'd tell a colleague.

    No forms and no special syntax. Write what you know, in your own words. Solvable picks out the facts that matter: who, what, when, and what isn't allowed.

  2. 02 · Questions

    It asks about what's missing.

    When something you didn't mention would change the answer, you get a question, not a guess. Any assumption it does make is listed, so you can correct it.

  3. 03 · Model

    It writes the model and shows its work.

    Every fact becomes a line in a mathematical model. Each line is tagged with the sentence it came from, so you can check that it understood you.

  4. 04 · Plan

    You get a plan, in your words.

    The answer comes back as a schedule, a route or a production order, with a short note on why it looks the way it does. Change one thing and only that part moves.

Use cases

Different businesses. Often the same kind of problem.

If you're deciding who, what, where or when, and there are limits on all of it, it's probably an optimization problem. A few examples:

Fig. 1

Delivery routes

Visit every stop with the vans you have, inside opening hours.

Example: 14 stops, 3 vans, 46% fewer km

Fig. 2

Staff rotas

Cover every shift, respect every day off, share the hours fairly.

Example: 6 people, 2 shifts, 7 days

Fig. 3

Production planning

Order the batches so the machines stay busy and the day ends early.

Example: 9 batches, 3 machines, done 2 h earlier

Fig. 4

Small energy systems

Charge the battery when power is cheap, use it at the evening peak.

Example: evening peak cut by a third

Fig. 5

Farm planning

Decide what grows where this year, without breaking the rotation.

Example: 12 fields, 4 crops, one resting

No black box

Read every line. Change any of them.

A plan is only useful if you can trust it. So the model behind it is right there, written out. Every line says what it means and where it came from. If one is wrong, say so, and only that line changes.

Example · Fjord Bread deliveries

Optimal

What it means

For every van, whether it drives straight from one stop to the next.

Where it came from

“We have three vans and fourteen cafés to deliver to.”

Point at a line, or tab through them, to see what it means.

What do you still plan by hand?

Describe it the way you'd explain it to a new colleague. You'll see the model before you have to trust the plan.