start a project · Mesa, AZ and remote

Bring the workflow, not a spec

One inbox, read by Ken Valenzuela, the only person who will work on this. Tell me what the work actually looks like and where it breaks. I reply within two business days, and if this is not something I should build, I will tell you that instead of scoping it.

Direct

ken.valenzuela@consultedbykenough.iolinkedin.com/in/ken-valenzuela ↗github.com/KenValenzuela ↗kenvalenzuela.com ↗

Useful to include

  • What the workflow looks like today, including the parts held together by hand.
  • Who does the work and where it stalls or gets redone.
  • What you have already tried, and what about it did not stick.
  • Roughly when you need it, and whether anything is forcing that date.

No pitch decks needed, and no list to join. Consulted by Kenough LLC, Mesa, AZ, working remote across the Valley and beyond.

Plain description beats a requirements doc.

Send it

opens your mail app · no backend, no list, no tracking