What file formats do you accept?
Layered PSDs are the classic, but we work from anything that communicates the design: flattened JPG or PNG mockups, PDFs, or share links from any modern design tool. Layered files produce the most faithful results because we can extract exact values and assets, but we quote from flat previews every week. If all you have is a screenshot of an old site you want rebuilt, we can work with that too.
How fast is turnaround, really?
A typical single homepage may take three to five business days. Inner pages on the same design system often take one to two days each, while WordPress themes may take one to three weeks depending on layouts and structured content. These are broad planning norms rather than commitments.
Who owns the code you deliver?
You do, entirely. Full source files, no encrypted blobs, no license fees, no attribution requirement. Use it, modify it, resell it as part of your client work — it is yours. The only thing we retain is the right to describe the work anonymously, as in our portfolio, and we will skip even that on request.
Do you work white-label?
By default, yes. Most of our clients are designers and agencies whose customers never hear our name. Nothing in the delivered code identifies us, and we are happy to communicate through your project tools under your conventions if that keeps things tidy on your side.
What does 'free revisions' actually cover?
Any difference between the approved design and what we delivered — spacing, color, type, behavior — is fixed free, with no time limit on reporting it. Changes to the design itself after approval are new work and get quoted as such, clearly, before we do them. The line between the two is the approved design file, which is why our process makes approval explicit.
Will my site work in older browsers?
Current versions of major browsers are the normal testing baseline. Support for a specific legacy environment — still relevant in some institutional and industrial contexts — adds effort and can require compromises. The browser-support data at Can I Use helps define those tradeoffs.
Is your code accessible?
Accessibility fundamentals are baked into every build: semantic structure, labeled forms, keyboard operability, alt text, contrast-aware implementation, and reduced-motion respect. Formal conformance to a specific WCAG level, with documentation, is available as a scoped add-on — full audits involve work beyond coding, and we would rather price it honestly than sticker-claim conformance.
Can you also host the site or maintain it?
We are a build studio, not a host. We will happily deploy to your hosting, hand off to your developer, or recommend a setup that fits the project — but recurring infrastructure is not what we sell. For WordPress builds we document update-safe customization so any competent maintainer can take over cleanly.
Do you use AI code generators or conversion tools?
Not for deliverable code. We evaluate the tools constantly — it would be malpractice not to — and we wrote up our honest assessment in hand-coded HTML versus automated tools. The short version: generators are genuinely useful for throwaway prototypes and genuinely unsuitable for production code you will maintain for years. You are paying for code a human thought about, and that is what you get.
What do you need from me to start?
A useful brief includes the design format, page or layout count, deliverable type (HTML, WordPress or email) and deadline. Fonts and final imagery can follow later — the file preparation guide covers what helps and why.