Prototypes
The lab
Things we build quickly to test one idea, before deciding whether they deserve a name.
Anyone on the team can pitch an idea. Not every idea becomes a product, and most should not. This is where an idea gets a working prototype fast enough to find out cheaply whether it is any good.
Each prototype exists to answer one question.
Can a plain-language description become a plan? A task organizer that takes an unstructured description of a week and produces a sequence a person would actually follow. The question is whether the ordering is good enough to trust without editing.
What does a system that refuses to guess feel like to use? Several small tools built to say plainly when they do not know, so we can see whether that is reassuring or merely annoying. The answer shapes every other product here.
How something leaves the lab
A prototype either fails its test and is shelved without sentiment, or it earns the next stage: a real name, a live market, and a price. From there the lab’s team runs it and makes it earn, and its builder moves on to the next idea. A product stays with the lab as long as it pays its way, and it is sold only when a buyer can take it further than we can. That is why every product has its own code, documentation, and home on the web from the start. Shelving is what keeps the lab’s prototypes cheap.
Prototypes are named internally only. A name is a commitment, and these have not earned one.
If you want to know what we are testing now, email hello@royalcoastlabs.com.