What We're Looking For
We're not looking for every problem. We're looking for specific kinds of recurring situations that are worth solving.
Real, recurring situations
Problems you encounter daily or weekly, not hypothetical edge cases or occasional annoyances. If it only happens once a month, you probably don't need software—you need a checklist and patience.
Specific enough to picture
We should be able to understand exactly what's happening just by reading your description. Vague descriptions lead to vague solutions. Specific problems lead to focused tools.
Worth solving
Something you'd pay to fix, or that's costing you real time, energy, or money. If the friction isn't worth paying to eliminate, it's probably not worth building software to address.
Represents a pattern, not a unique situation
If you're the only person who experiences this exact problem in this exact way, it's probably not a good fit for a product. We build for categories of people, not individuals.
What This Isn't
Understanding what we're not is as important as understanding what we are and what we're not.
A request for custom development
We don't build bespoke solutions for individual companies or situations.
A consulting inquiry
We're not available to help you solve your specific problem through services.
Guarantee we'll build it
Most problems won't become products, even if they're real and worth solving.
A way to get something for free
We don't build products just because someone asked. We build because we think something is worth solving.
It's simply a way to share what you're experiencing. Sometimes that informs what we build. Often it just helps us understand a domain better.
How This Works
This isn't a form. It's a conversation. We read everything that comes in. We respond thoughtfully. We're not afraid to say "no."
You describe the situation
What you're dealing with, how often it happens, why it matters, and what you do now.
We read everything
Every submission gets read by a person, not filtered by automation.
We ask questions if it's interesting
If the problem seems like something that might fit what we build, we'll follow up to understand it better.
We decide what fits
Based on whether it aligns with how we work, whether it represents a pattern, and whether it's worth sustained attention.
Share What You're Experiencing
If you're dealing with something that keeps costing you time, focus, or clarity, we want to hear about it. Not every problem becomes a product. Most don't. But every product we build starts with someone experiencing real friction in real work.
Tell Us About Your Problem
We'll read everything. We promise.
What Happens Next
We read everything that comes in. We respond thoughtfully. We're not afraid to say "no.". Usually within a day or two.
We read everything that comes in
Every submission gets read by a person, not filtered by automation.
We respond honestly
If it's interesting, we'll ask more questions. If it's not a fit for what we build, we'll tell you that directly rather than leaving you wondering.
We might explore it
If the problem fits our criteria—real, recurring, representative of a pattern—we might build something. That process takes weeks to months.
You'll be among the first to know
If we build something related to your problem, we'll invite you to try it early. No obligation. No strings attached.