The studio
A new studio, run in the open
NinjaMunk is a remote design and engineering studio building websites for companies that treat their site as a sales channel. We are new, we say so, and we make it easy to judge the work before you commit anything.
Commitments
Four things
we hold to
- 01
Senior people only
The person who takes your brief is the person who designs and builds it. Nothing is handed to a junior team once the contract is signed, and there is no account layer rewriting what you asked for.
- 02
Written before visual
Structure, messaging and page intent are agreed in writing first. Design reviews are then about craft and clarity, not a debate over what the page is supposed to do.
- 03
Measured, not asserted
Performance, accessibility and crawlability are verified with tooling before launch, and the reports are handed to you. You do not have to take our word for any of it.
- 04
No lock-in
You own the repository, the domain, the analytics and the hosting accounts from day one. Retainers are optional, monthly and cancellable without penalty.
Straight answers
What you
should know
We are new — and we do not hide it
NinjaMunk launched recently. There are no client logos on this site because we will not borrow credibility we have not earned. What we publish instead is our process, our standards and concept builds you can inspect in detail.
How we price without a track record
Fixed scope, fixed price, agreed before work starts. If the estimate turns out to be wrong on our side, that is our cost to absorb — not a change request sent to you halfway through.
How you can judge us before committing
Read the concept projects, run this site through Lighthouse, and send us a real problem. The quality of the first reply will tell you more than a portfolio of screenshots would.
Standards
Trust you can
verify yourself
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.
- 01
Transparent process
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.
- 02
Performance first
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.
- 03
Accessibility commitment
WCAG 2.2 AA as the working baseline, verified with automated tooling plus manual keyboard and screen-reader passes before we call anything done.
- 04
SEO ready at launch
Semantic markup, heading hierarchy, canonical rules, structured data and internal linking implemented in components rather than bolted on afterwards.
- 05
Responsive by construction
Layouts composed at real breakpoints on real content, with touch targets, reading measure and image delivery checked on mid-range devices.
- 06
Clean, documented code
Typed end to end, linted, reviewed and commented where intent is not obvious. A developer who has never seen the project can read it.
- 07
Scalable architecture
A content model and component library designed for the pages you have not written yet, so growth does not require a rebuild.
- 08
Long-term maintainability
Low dependency count, documented upgrade paths and handover notes. You own the repository and every account from day one.
Why NinjaMunk
Hired for judgement,
kept for results
Six commitments that shape every engagement. They are the reasons clients stay, and the reasons we occasionally tell a prospect we are not the right studio for the job.
- 01
Revenue is the brief
We start with what a customer is worth and how many you need. Design decisions get argued against that number, not against personal taste.
- 02
Speed is a contract term
Every build ships against a page-weight and Core Web Vitals budget. If a page misses it, the page changes before launch — it does not become a phase two.
- 03
Search built into the structure
Semantic markup, heading hierarchy, schema and internal linking are part of component work. Crawlers read exactly what your buyers read.
- 04
Built to be extended
Typed components, documented tokens and a content model that anticipates the pages you have not written yet. New sections take hours.
- 05
Senior people only
The person you brief is the person who designs and builds. No account layer translating your requirements into something else.
- 06
A partnership with an exit
You own the code, the repository and every account. Stay on a retainer because the work is worth it, not because leaving is painful.
Process
Six stages,
nothing improvised
You always know which stage the project is in, what is being decided, and what we need from you next. No silent weeks, no surprise invoices.
01
Interrogate
A working session on revenue, buyers and objections. We establish what the site must prove, what it currently fails to do, and how success will be measured six months from launch.
Output: written brief, success metrics, constraints
02
Map
Competitor teardown, search demand analysis and analytics review. Evidence sets the sitemap, the keyword targets and the order in which arguments appear on the page.
Output: sitemap, keyword map, message hierarchy
03
Design
Design system first, then key pages composed on real copy. Reviewed in the browser at mobile and desktop widths, never as flat images with placeholder text.
Output: design tokens, page designs, prototypes
04
Engineer
Component-driven React and TypeScript, typed end to end, measured against a performance budget on every commit. Accessibility checks run in the same pipeline as tests.
Output: production build, component library
05
Launch
Redirect mapping, analytics, Search Console, structured data validation and a recorded walkthrough so your team can publish confidently on day one.
Output: live site, tracking, training
06
Compound
Post-launch we watch the numbers that matter and keep improving them: page speed regressions, ranking movement, enquiry rate and the pages losing attention.
Output: monthly reporting, iteration backlog
Next step
Tell us what the
site has to do
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.