The context
A problem worth solving.
An online flower retailer has very different workflows across customer support, marketing, storefront and product data. The challenge is connecting useful AI to each team’s actual information and tools.
My contribution
What I brought to the work.
Built and evolved the internal AI platform, the support applications and Chrome extension, the marketing image tools, the company knowledge workspace, storefront integrations and the DIY-kit data migration, from early prototypes in 2025 to production tools in 2026.
The product
What it makes possible.
01Customer service AI
Four support apps, shared case history and a Chrome sidepanel, in production since January 2026. They replaced the paid AI writing tool the team used before, which saves about $24,000 a year. See the Customer service AI case study.
02Company Second Brain
Team knowledge around a personal memory, with a chat that chooses which knowledge to read and lists its sources. Two teams’ knowledge is in so far. See the Company Second Brain case study.
03Product imagery
Image Studio and Preset Creation for consistent product photos. See the Image Studio case study.
04Content from customer questions
Six months of support conversations classified into customer-question topics and coverage gaps, with a review queue of FAQ and blog drafts built in June 2026. Nothing publishes without a person’s approval. See the Content Engine case study.
05Storefront
The AI Floral Assistant, rush-order requests and Share Your Flair contest entries. See the AI Floral Assistant and Storefront requests case studies.
06DIY kit data migration
Farm spreadsheets matched to store products, with recipes, purchase links and 2,789 arrangement plans written to a test copy of the store and checked against their sources. See the DIY kit migration case study.
07Proposal Manager
Implemented supplied wireframes for event planning, flower recipes, presentations and shopping lists. Not launched; work paused when the kit migration took priority. See the Proposal Manager case study.
At a glance / simplified product view
- 01Team workflows
- 02Connected AI tools
- 03Human review
Inside FiftyFlowers
The products, one by one.
Engineering choices
The decisions behind the interface.
01Bring related tools into one platform.
Support applications, a browser extension, marketing tools and company knowledge grew into one internal platform while keeping the different workflows each team needs.
02Make the rollout boundaries visible.
Customer-service knowledge supports the operational apps; marketing and engineering knowledge are developing parts of a broader company second brain and are not presented as equally mature.
The platform combines production workflows with MVP and beta work. The product groups above identify those differences.
Where it stands
In production, and still growing.
The tools are at different stages: the support apps and the rush-order form are in production, the shopping assistant ships in the store theme behind the company’s A/B test, Share Your Flair processing has handled every 2025 entry, the knowledge workspace is an MVP, and the kit migration is complete on a test copy of the store.