For Designers.

We're not a full-service agency. We don't have designers on staff, and that's deliberate. It means we're not competing with you—we're complementing you. When a client needs both design and development, we work alongside your team rather than trying to absorb your role.

We've built Craft sites from designs delivered by large agencies, boutique studios, solo freelancers, and in-house design teams. The quality of collaboration depends less on the size of the design team and more on a few specific practices that we'll lay out here.

The best projects we've worked on share a common trait: the design team and the development team talk to each other early and often, rather than treating the design as a finished document that gets thrown over a wall.

We work with whatever tools your team uses. Figma is most common and our preference for collaboration, but we're equally comfortable with Sketch, Adobe XD, or well-organized PSDs. What matters more than the tool is the completeness of the deliverables.

• Complete page designs for all unique templates (not every page, but every distinct layout)
• Responsive breakpoints showing how layouts adapt across desktop, tablet, and mobile
• Component design system showing the reusable elements and their variants (buttons, cards, form fields, navigation states)
• Interactive states for hover, focus, active, loading, error, and empty states
• Typography scale and color system documented clearly
• Content-dependent edge cases—what happens when a title is 4 words? 40 words? When there's no image? When a list has 3 items versus 30?

• Animation and transition specifications
• Accessibility annotations (focus order, ARIA label guidance)
• Content model suggestions (which content should be editable, what relationships exist between content types)

The most impactful thing you can do is talk to us before the design is final. Not because we want to constrain your creativity, but because early awareness of technical realities prevents expensive surprises.

If you're designing a complex filtering interface, we can tell you what's technically feasible with Craft's content model and your chosen search backend. If you're designing an international site, we can explain how Craft's multi-site system works and how that might influence your layout approach for different languages. If you're designing a content-heavy page with 15 related entries, we can flag the performance implications before you commit to a design that requires 40 database queries.

These conversations take 30 minutes and save weeks.

We implement your designs as designed. We don't make creative decisions, substitute fonts, approximate spacing, or "simplify" interactions without discussing it with you first. If something in the design doesn't translate to the web exactly as drawn, we'll explain why and work with you on an alternative—we won't just quietly change it.

You provide the key breakpoints; we handle the in-between. For the transitions between your designed breakpoints, we make sensible engineering decisions about how elements reflow, resize, and reorder. If a particular transition needs specific creative direction, flag it in the design deliverables and we'll implement it exactly.

We design the Craft content model to support your design's content needs. If your design shows a hero with a headline, subheadline, image, and CTA—those become editable fields. If your product page design implies relationships between products—those become Craft relation fields. We think carefully about how content editors will populate the designs you've created and build the editing experience to match.

If something in the design will be technically expensive to implement, we'll tell you—with specifics. Not "that's hard" but "that interaction requires a custom JavaScript library that will add 40kb to the page weight and take an additional three days to build and test." Then you decide whether it's worth it. Usually there's a simpler approach that achieves 90% of the same effect.

An optional but valuable kickoff where we align on technical constraints, CMS capabilities, performance goals, and any architectural decisions that will influence design. For headless projects, this conversation is essential. For standard Craft builds, it's a 30-minute call that prevents misalignment.

We're available for questions as they come up. "Can Craft do this?" and "Is this pattern feasible?" are exactly the kinds of questions we want to answer while the design is still fluid—not after it's been presented to the client and approved. Some teams prefer a weekly check-in during the design phase; others prefer async questions in a shared Slack channel.

We review the final designs together—ideally in a live session, not asynchronously. We walk through each template, flag questions, identify any edge cases the design doesn't address, and agree on priorities if budget requires phased implementation. This review typically takes 1-2 hours and surfaces issues that would otherwise become development blockers.

We share staging access early so you can see the implementation taking shape. You review and give feedback on sprint deliverables. We flag any places where the implementation deviates from the design (and why). The goal is continuous alignment, not a reveal at the end.

A final design review in the staging environment. You verify that the implementation matches your intent across breakpoints, with real content, and in the edge cases that matter. We address any issues before going live.