2025
tmrw.io
Marketing site contributions for a public learning platform
OVERVIEW
What it is
While at TMRW.io as Junior UI/UX Designer & Manual QA (June 2025 to June 2026), I contributed to the public marketing website at tmrw.io. The focused website push ran roughly August to October 2025. Work covered icons, layout, imagery, and hands-on QA across pages, CTAs, media, and copy.
Employee / contractor contribution. Brand, product, and IP belong to TMRW.io. This case study only references publicly visible pages and my own description of the work.
MY ROLE
How I contributed
I joined after a year at Octivo. On the marketing site I designed icons in Figma, shaped page layout, created imagery, QA tested pages and interactive details, and presented work in weekly reviews with staff and developers. I did not own the brand or the full product roadmap. I contributed design and quality work as part of a wider team shipping the public site.
PROBLEM
The challenge
A public marketing site for a learning platform has to explain a complex ecosystem clearly: what Genesis and Cosmos are, who they are for, and how to take the next step (try Genesis, join a waitlist, read more). Layout, icons, imagery, and working CTAs all have to hold together so visitors can scan, understand, and act.
CONTEXT
Where it lives
tmrw.io is the public front door for TMRW Education and Learning Software. Visitors see product introductions, solution explanations, news, and paths into Genesis or Cosmos interest flows. This case study sticks to that public surface. It does not include internal Figma files, the full design system export, Genesis app UI behind login, or bug tickets.
VISUALS
From the live site
[add screenshot of homepage] Full-width hero from https://tmrw.io showing the primary headline (for example the AI-powered Experience Builder introduction), supporting line, and main CTAs such as Find out more / Try Genesis. Capture desktop first viewport, no private UI.
[add screenshot of ecosystem section] Public Solutions area introducing the TMRW ecosystem, Genesis, and Cosmos at a glance. Show section heading plus the product cards or columns visitors see without logging in.
APPROACH
What I did
01
Icons
Designed icons in Figma for use on the marketing site, aiming for a consistent set that supports scanning of features and sections without competing with headlines or photography.
02
Layout
Contributed to page layout so hierarchy, spacing, and section rhythm supported the story of the TMRW ecosystem and the paths into product interest.
03
Imagery
Created imagery for the public site to give sections atmosphere and product context, paired with the written messaging already on the page.
04
QA
Manually QA tested pages, CTAs, media, and copy before and after handoff. Checked that links and buttons behaved as intended, media loaded cleanly, and copy matched the intended messaging on public pages.
[add screenshot of Genesis marketing section] Public Genesis pitch on tmrw.io (Create, innovate & educate / no-code builder messaging). Include any feature callouts and the See Genesis Features or Try Genesis CTA. Do not capture the logged-in Genesis app.
[add screenshot of icons on a public page] Close crop of marketing icons as they appear on a live tmrw.io section (feature row, solution cards, or similar). Prefer a crop that shows several icons together so the set reads as a system.
[add screenshot of imagery + layout] A mid-page section where custom imagery and layout work together (for example Cosmos audience columns, news cards, or a product intro with supporting visual). Desktop width, publicly visible content only.
[add screenshot of a secondary public page or footer] Optional: Why TMRW, Resources / Knowledge Centre listing, or the footer with Platform links and Acknowledgement of Country. Useful to show breadth beyond the hero.
PROCESS
How the work moved
01
Design in Figma
Icons, layout explorations, and imagery started in Figma, then moved into reviews with staff and developers.
02
Weekly reviews
Presented work in weekly reviews so design choices and QA findings could be discussed with people shipping the site.
03
Test the public pages
Walked public pages end to end: scan the story, exercise CTAs, check media, and catch copy or interaction issues before they sat on the live marketing surface.
OUTCOME
What I learned
Working on a live marketing site taught me to balance craft with ship pressure: icons and imagery need to feel intentional, layout has to carry a dense product story, and QA is part of design quality, not a separate afterthought. Presenting in weekly reviews made the feedback loop concrete. I learned to describe contribution clearly without overstating ownership of brand or product.
SNAPSHOT
At a glance
- ROLE
- Junior UI/UX & Manual QA
- SITE PUSH
- Aug to Oct 2025
- LIVE
- tmrw.io