Singapore · Venture studio
We build the software design practices keep wishing existed.
Flynt Labs turns the problems that keep recurring inside architecture, landscape and design studios into focused, practical products. Two are live and in daily use.
Two products
Live in production, not in beta
Built inside practice
By people who ran these spreadsheets first
Singapore
GMT+8, built for Asia-Pacific first
One sector
Architecture, design and landscape
01 ResourcePlanner
Stop the feast or famine. Plan your practice.
A practice runs ten to twenty fee-capped projects with a mostly fixed team, and the staffing plan lives in a spreadsheet that is stale the moment it is saved. The margin problem surfaces at month-end, after the hours are already spent.
See capacity six months ahead
Every team member’s allocation across all live projects in one view — so you know before you pitch whether the team can deliver.
Staff the right phase, not just next week
Rate cards, sub-consultant lines and SD/DD/CD stages linked to the fee, so margin is visible while you can still act on it.
Spot overloads before they become problems
A senior architect at 130% shows up as a red alert, not as a surprise at month-end. Multi-office holidays, leave and contractor timesheets included.
02 GreenCurate
Which plants will actually survive in your space?
Specifying planting means hours of cross-referencing across PDFs, nursery catalogues and databases written for temperate climates — and the one thing the client actually sees, a palette they can read, gets rebuilt by hand on every project.
Pick plants the way a designer picks colours
Describe the space in your own words and GreenCurate composes a palette that will thrive there — 13,542 species across 53 recorded fields.
Build a palette that holds up
Selections become project palettes with aggregate height ranges and a combined bloom calendar, calculated for you.
Hand the client something readable
Export a client-ready board as a PDF or a link — no licence limits on the imagery, because we own all of it.
03 How the studio works
A studio, not an agency. We keep what we build.
Watch the workflow
We sit inside the practice and follow the job that keeps going wrong — usually the one held together by a spreadsheet.
Cut the scope hard
One problem, one product. We would rather do the resourcing properly than do everything approximately.
Test it on real projects
Live fee stages, live deadlines, real teams. Nothing ships on the strength of a demo dataset.
Run it as a product
It stays ours. We keep shipping into it for years, not until launch day.
04 Who we are
Two founders, one practice-shaped point of view.
Both products came out of the same frustration, on the same kind of project, on the same deadlines you are working to. We are building for the studio we came from.
Ben Yap
Co-founder
Cliff Chew
Co-founder
05 In the lab
camie.app
A character-driven interface experiment — state-driven animation as a way to make software feel answerable. An early concept.
Not shipping yet