Building smarter
When the side project becomes the work.
This domain began as StocksWatch, a source-linked research desk for NBIS. The project grew to include downloadable research materials and a sandbox purchase flow. This note records the decision to simplify, not a claim of revenue or proven demand.
What was tried
The site combined a static Astro build with market-data refreshes, research guides and a free kit. A paid workflow pack was previewed, and a separate sandbox delivery service was developed. Production sales remained closed.
The technical work was real, but a functioning preview and a sandbox checkout did not answer the most important question: whether the material solved a problem people cared enough about to return.
Why change direction
The stated goal was a useful, inexpensive project that fits around a career and a small business. Daily data dependencies and purchase-delivery work created responsibilities before demand had been established.
The more useful starting point is closer to Jacob’s experience: practical engineering, automation and systems. StocksWatch becomes a source of lessons rather than a commitment to maintain a financial product.
What changes in this version
The new site keeps the existing domain and static hosting approach. Its core is a few guides, a resources page and a short introduction. The design has no account, checkout or newsletter form.
The old research pages are retired. The investment newsletter is not being repurposed for a different audience. Existing external accounts and billing arrangements need their own review; changing the website does not cancel them.
What has not been established
There is no validated revenue, traffic growth or measured time-saving claim to report here. This is a smaller hypothesis: useful material drawn from actual work may be easier to maintain and more helpful to readers.
The next evidence is modest: whether someone tries a guide, asks a specific follow-up question, or returns with a problem it did not solve. Publishing more pages is not evidence by itself.
What to carry into another project
Before adding a service, write down what user problem it solves and what ongoing obligation it creates. Keep the product small enough that one useful improvement does not require operating several unrelated systems.
This approach may suit someone building alongside other responsibilities. It is less suited to an experiment whose central purpose is operating a live data service; that requires a different maintenance commitment.
General educational guidance. Adapt it to your environment, permissions and risk. Examples are illustrative unless identified as project history.
← Back to all guides