GrowGreen Platform

Platform, Dashboard & Design System · Belgium

Result: The customer account behind a Paulownia tree storefront: nine sections built on GrowGreen's own design system

The brief

Someone who buys trees on a plantation waits years for the timber. In between, the account is the product: it has to show what they own, where it stands and what has been paid, and keep money credited apart from money promised.

GrowGreen sells for Clearworld and the grower allocates the trees, so the account also has to show what is allocating, what is planted and what was harvested, plot by plot.

What we built

We are building the GrowGreen platform behind the storefront: one repository laid out for the website, the customer account, the API and the design system, hosted on Railway. The website and the design system are built; the API and the background jobs come next. The customer account is where people who bought Paulownia trees follow every one of them. It is built from GrowGreen's own design system: tokens, components and screens, in a dark and a light theme.

The account has an overview of the holding, a map of every plot with each tree in a register (plot, planting date and status), payouts with every credit to date and what is due next, an activity feed of orders, allocations and credits, documents filed by year, a monthly subscription and referral codes. Every screen carries the risk notice and says who is who: Clearworld BV sells the trees and holds the contract.

The design system has a playground beside it, where a change to a component shows up in the gallery and in the dashboard at the same time. A read-only copy runs on a private address for the team and is rebuilt within minutes of every change.

The result

The storefront at growgreen.finance is live. The customer account and the services behind it are in build on the same platform. The screens on this page run on the real components with a made-up customer; no customer data appears here.

The storefront has its own page: GrowGreen, the Paulownia tree storefront.

What this means for a business like yours

If your customers buy something they follow for years, the account they sign in to is what they judge you by between purchases. This is our Automation & AI work joined to a website build: the design system, the screens and the app. The first step is a free 15-minute call about what you are building.

Numbers

  • 9 Sections in the customer account
  • 34 Components in the design system
  • 4.5:1 Minimum text contrast, in both themes
  • 2 Themes, dark and light

What we delivered

  • Platform repository laid out for the website, the API and the UI
  • Hosting on Railway
  • Design system: tokens, components and screens
  • Customer dashboard with nine sections
  • Plot map and tree register
  • Payouts, activity and documents by year
  • Subscription and referral screens
  • Playground and a private read-only copy for the team

The dashboard

  • Overview: The holding at a glance: trees, the next return, the balance and the latest activity
  • Your trees: Every plot on a map, every tree in a register with its planting date and status
  • Payouts: The balance, every credit to date and what is due next, kept apart from what is promised
  • Documents: Every document issued to the customer, filed by year
  • Referrals: A referral code and the friends who used it

Overview in the GrowGreen customer account dashboard, dark theme

Where this fits