Everything worth knowing before we work together — no fluff, just straight answers.
30 minutes. We talk through what you're building, what's broken, and whether there's a real fit. No pitch — just a direct conversation about your actual problem. You'll leave with clarity regardless of whether we work together.
Fill out the short form on the contact page and pick the option that best fits what you need. I'll follow up within one business day to schedule the free 30-min call. That call is where we figure out scope, timeline, and whether it's a fit — before anything is signed.
Bring a link to your current product or site, a rough sense of what's not working, and any timeline constraints. You don't need a brief, a deck, or a clear plan — that's what the call is for. The more specific you can be about the problem, the more useful the conversation will be.
Yes. The UX Audit + Direction tier is built for exactly this: you need clarity before committing to a full build. Many founders start there, then come back for the full system once they've validated direction. If you're pre-revenue but have a clear product vision, let's talk.
SaaS, AI tools, fintech, creator tools, e-commerce, professional services, and product-led startups are the most common. The work is interface and UX — if you have a digital product or site that needs to communicate clearly and convert, the industry is usually secondary to the quality of the problem.
Tier 1 (Audit): typically 5–7 business days from kickoff. Tier 2 (Design System): 1–2 weeks. Tier 3 (Full Build): 2–3 weeks depending on scope. These assume prompt feedback during the process. Add-ons and large scopes are discussed and confirmed before kickoff — never a surprise mid-project.
Each project tier includes one round of revisions after the initial delivery. This covers direction adjustments, copy changes, layout tweaks, and visual refinements within the original scope. Additional rounds or scope additions are quoted separately — and always before the work is done.
You'll see a direction check roughly midway through, so nothing arrives cold at final delivery. For audits this is an early findings summary; for design systems it's a direction pass on color, type, and structure before full mockups are built. The goal is no surprises in either direction.
Post-delivery changes are handled one of two ways: as a small scoped addition (quoted at an hourly or flat rate), or under a retainer if you need ongoing design support. Most past project clients who want continued work end up on the monthly retainer — it's more efficient for both sides.
Absolutely. I've worked inside established design systems many times — adapting to what exists rather than rebuilding from scratch. Bring whatever you have and we work from there. If the existing system has gaps, I'll surface them during the audit and we decide together how to handle them.
Design: Figma (primary), with Framer for motion/prototype work. Code: HTML, CSS, JavaScript — delivered as clean, documented files. AI layer: proprietary workflow using multiple models for pattern analysis, gap detection, and velocity. You don't need to understand the tools — you just get the output.
Three things drive where you land: page count, interaction complexity, and whether AI-native patterns are involved. A focused 3–4 page site with standard layouts is toward the lower end. A multi-section product with complex flows, onboarding, dashboards, or heavy animation is toward the higher end. The exact number is confirmed on the systems call — before any work begins.
Not as primary deliverables. The work is interface design, UX systems, and front-end code. That said — copy, hierarchy, and message clarity are deeply connected to UX, and I'll flag and advise on those during an audit. If you need a dedicated copywriter or brand strategist, I can point you toward people I trust.
No. The code delivered in Tier 3 is front-end: HTML, CSS, and vanilla JS. Connecting it to a CMS, database, or backend is a separate conversation — and can be scoped as an add-on if you need a CMS or platform integration alongside the design work.
You own everything. All Figma source files, code, assets, and documentation transfer to you at final delivery. No licensing, no ongoing fees, no strings. This applies to retainer work too — anything produced during the engagement is yours.
Audit decks are delivered as annotated PDFs and a shared Figma file. Design systems include the Figma source file plus a design system PDF. Tier 3 builds include all of the above plus a clean folder of HTML/CSS/JS files, exported assets, and a short readme for handoff. Everything is organized for your team to pick up without asking questions.
Yes, for client work involving unreleased products, internal systems, or sensitive business data. Send your standard NDA before the call and I'll review it. I use mutual NDAs as a default for retainer relationships. For short project engagements, a confidentiality clause in the project agreement is usually sufficient.
Project work: 50% upfront to hold the start date, 50% on delivery. Retainers: billed monthly at the start of each cycle. All invoices are Net 30 (due within 30 days). Preferred payment is ACH. Invoiced through two percent LLC.
Yes, but it's handled explicitly. If you want to add pages, features, or deliverables after kickoff, we scope and price the addition before any work on it begins. No surprise invoices at the end, and no quietly absorbed extra work either. Scope clarity is how the timeline holds.
The upfront deposit is non-refundable once work has begun — it covers research, setup, and reserved time. If a project is cancelled before kickoff, the deposit is returned minus any pre-work time already logged. The goal is to scope tightly enough upfront that cancellations don't happen. That's what the systems call is for.
The tiers are fixed-scope at fixed prices — that's what keeps delivery fast and predictable. If your scope is genuinely smaller than what a tier covers, we can discuss a reduced scope at a reduced price. What doesn't work is the same deliverables at a lower price. The value is in the output, not the time.
We'll talk through your specific situation — what you're building, what's not working, and whether there's a fit. You'll leave with clarity either way.
Not a call person? Send a message through the contact form with your question or situation and I'll write back with a straight answer — usually same day.