How it works

Small, written down, finished.

No procurement. No proposal deck. No discovery phase that bills for itself. For a scoped tool the whole thing can happen inside a week.

The sequence

  1. You tell us the problem

    Four fields, or just text us. However you describe it is fine; we will ask the sharpening questions on the call.

  2. We answer within 24 hours

    Yes, no, or one question. A no comes with a reason.

  3. A call with the developer who would build it

    Not a sales call, and not an account manager. You talk to the engineer, who works with you to design something custom to your situation: what would actually move your numbers, what is buildable in the time you have, and whether something off the shelf already does it.

  4. A scope you can read in a minute

    What you get, what you explicitly do not, and the date. Not a contract, since nobody here can sign one, but specific enough that we can both tell later whether it happened.

  5. We build it

    One day to one week, depending on scope. You get access from the start rather than at handoff, and something working early rather than a reveal at the end.

  6. Handoff

    Documentation written for whoever comes after you, a walkthrough, and an honest list of what is fragile. It is all already in your accounts, so there is nothing to transfer.

What this costs you

The work: nothing, ever

Every hour is donated by an individual volunteer. Nobody is compensated, including the person coordinating. No invoice now, none later.

Uncompensated work by an individual is not a campaign contribution under 11 C.F.R. §§ 100.74 and 100.94. No cap, and nothing for a treasurer to report. Your counsel should confirm how your state handles it, but this part is settled.

Infrastructure

Some of what we build needs somewhere to run and some of it does not: a script that produces a file needs nothing at all. Where hosting is involved we will work out the arrangement with you on the call, and the guiding rule is that you end up owning whatever runs.

What we never do

  • Invoice you
  • Accept money or reimbursement from you
  • Take equity, revenue share, or a cut of anything
  • Hold your data or your licences in accounts we control

What we need from you

  • One person who answers. Weekly, and able to decide alone.
  • Access, early. Accounts, exports, credentials for whatever we integrate with. Waiting three weeks for a CSV is the most common way a volunteer project dies.
  • The real deadline. Not the date you would like. The date after which the thing is useless.

Ready to start?

Bookis Worthy

Bookis Worthy

It's 10:07 AM where he is. Usually replies the same day.

LinkedIn·GitHub·Rather write it out?