Concept projects
NinjaMunk launched recently, so there are no client logos here. Instead we publish concept builds with the full reasoning attached — the business challenge, the research, the UX decisions, the SEO plan and what the work would be expected to change.
A note on these projects: every build below is a self-initiated concept project, not a client engagement. Company names are invented, no results are claimed and nothing here was paid for. They exist so you can judge our thinking and our standards before you spend anything.
Meridian Capital
Financial advisory and wealth management · 2026
A financial advisory site built around one question: can a prospect understand the offer and book a call inside a minute? Sections that answer nothing were cut.
Read the full case studyOrbit Analytics
B2B SaaS analytics · 2026
A marketing site and dashboard shell sharing one token set, so the product a buyer sees in a screenshot is the product they get after signup.
Read the full case studyNorth Supply Co.
Trade and industrial supply ecommerce · 2025
A trade supplier storefront designed for search: disciplined category structure, honest product detail, and image delivery tuned for weak site-visit signal.
Read the full case studyKindred Clinic
Private healthcare and multi-practitioner clinics · 2025
A multi-practitioner booking journey built for people in a hurry and people using a screen reader — the same flow, tested both ways, no separate accessible version.
Read the full case studyStandards
We are a young studio, so we do not offer borrowed authority. We offer standards you can check — in this site's own code, reports and structure.
Scope, dates and a fixed price in writing before anything is booked. A shared board and a working link you can open at any point in the build.
A page-weight and Core Web Vitals budget agreed at scope and checked on every commit, with the Lighthouse reports handed to you at launch.
WCAG 2.2 AA as the working baseline, verified with automated tooling plus manual keyboard and screen-reader passes before we call anything done.
Semantic markup, heading hierarchy, canonical rules, structured data and internal linking implemented in components rather than bolted on afterwards.
Layouts composed at real breakpoints on real content, with touch targets, reading measure and image delivery checked on mid-range devices.
Typed end to end, linted, reviewed and commented where intent is not obvious. A developer who has never seen the project can read it.
A content model and component library designed for the pages you have not written yet, so growth does not require a rebuild.
Low dependency count, documented upgrade paths and handover notes. You own the repository and every account from day one.
Next step
Send the goal, the deadline and a budget range. You will get a considered reply within one working day — including an honest answer if we are the wrong studio for it.