09/Contact

Tell me whatshould work better.

You don’t need a technical specification. Start with the problem.

The interesting projects usually start with something repetitive, fragile, manual, disconnected, or living in someone’s head. Tell me what that is.

  • REPETITIVEThe same export, reformatted the same way, every week.
  • FRAGILEOne sheet that breaks whenever a column moves.
  • MANUALNumbers re-typed from one screen into another.
  • DISCONNECTEDTwo systems that both hold the truth, differently.
  • IN SOMEONE'S HEADA rule nobody wrote down, applied from memory.

The brief

Eight fields, and only five of them matter.

Enough to tell me whether this is a system problem, a process problem or neither — and nothing beyond that. No budget field, no company size, no dropdown asking how you heard about me.

It goes to a server-side handler that checks it, limits how often one connection can post, and records it. If any of that fails, the form hands you the same text as an email.

THE BRIEF

A first name is enough.

Where the reply goes. It is used for that and nothing else.

Only if it is relevant. Independent work is just as welcome.

A shop, a team, a product, a process. One line is plenty.

The one that matters. Done by hand, done twice, done from memory, or done across four tabs — describe it the way you would to a colleague.

Useful even as a guess. “Nobody re-types it” is a complete answer.

PROJECT TYPE

Closest wins. It only sets my expectation before I read the rest.

TIMELINE — OPTIONAL

“Still exploring” is a perfectly good place to start.

Nothing is kept in your browser, and nothing here is shared onward.

Rather not use a form? hello@jdenandro.com reaches the same person, and is the most direct route there is.

What happens next

  1. FIRSTI read it and work out what the problem actually is, which is not always the one described.
  2. THENYou get a straight answer: what I think it is, roughly what shape a system for it takes — or that it is not a fit, and who or what it should go to instead.
  3. AFTER THATIf it is worth building, we scope it properly before anybody writes code.

DIRECT

hello@jdenandro.com

Not ready to write one yet? Read what has already been built and see whether any of it looks like your problem.