(STEMWISE · SKETCH TO FEATURE)

From Sticky Note to SaaS Feature in 3 Weeks

Her sketch started the mother-plant feature, which tracks the big plants every cutting is taken from. Below is that sketch, the DMs it came in, and what shipped.

(TL;DR)

SITUATION
A wholesale grower already using Stemwise ran her mother plants, their variants, and their growing stages on paper, then sketched what she needed it to track.
WHAT I DID
I read her sketch and DMs, built her own stage names into the database, and shipped the feature.
RESULT
The feature shipped. She is moving her collection into it now.

(THE ASK, IN HER WORDS)

A wholesale grower’s actual sticky notes: stock, variants, TC/corm/starter rows.

Three DMs, identity withheld. Her words, unedited.

  • I built a tracking setup for myself. This is what I was thinking of for the Family tree.

  • Can I beg of you to add corm to the stages?

    I have 100 varieties of corms and about 60 varieties of TCs with some overlap.

  • Having a corm means I need to track where it came from so I can track if it is stable from a TC up the line. There are a lot of “reverts” around right now.

A wholesale customer · identity withheld

(THE TRANSLATION)

Her language, into the database.

Mother plants, growing stages including corm, which the database had no slot for, and lineage, so a plant that reverts still traces back to its parent. Three sentences of hers meant a real change to the database, not flipping a setting.

Her wordsWhat changed in the database

“corm”
A growing stage the database had no slot for.
“reverts” · “track if it is stable from a TC up the line”
Lineage, so a plant that reverts still traces back to its parent.
“mother plants”
The mother-plant record every cutting is taken from.

(SHIPPED)

Live Plants lineage view: variety, stage, and status filters, with a mother-plants toggle.
3 weeks · request to livecould’ve been faster -- had actual work to do.SEE IT LIVE ↗