Interfaces people understand.
Websites that convert.

Two things. I design digital products: SaaS platforms, crypto apps, mobile apps, dashboards. And I design websites and landing pages built around conversion. The first comes from 5 years of building products from zero, the second from 1.5 years at a US CRO agency.

Founders and small product teams. Sometimes it's a pre-launch product that needs a real visual direction and a working flow. Sometimes it's a live site that gets traffic and doesn't convert. The common thread is a team that wants to ship rather than explore.

No. It's me. You talk directly to the person doing the work. When something falls outside my range, I say so instead of stretching.

SaaS, crypto, fintech, iGaming, and a lot of general web work. Crypto specifically: I've worked on AirNFTs and PerpMate, so wallets, transactions, and onboarding people who have never used one are familiar territory.

A fixed amount of design time each month, used however you need it. Priorities get set at the start of each cycle. It suits teams with steady design needs but not enough to justify a full-time hire.

Yes, when the scope is clear enough to price honestly. When there are real unknowns, a sprint protects both of us better than a number pulled from optimism.

A two-week sprint. Enough to deliver something real, and enough for both of us to tell whether this is working.

Yes. Most clients start with a sprint and move into a retainer or a full project after.

Usually within a few days to a week depending on what's in progress. Rush availability comes up, so it's worth asking.

Whatever you have: existing designs, a rough brief, references you like, or just a conversation about the problem. If you don't have references, I can put together a moodboard so we align on direction before real work starts.

Your preference. Weekly calls, async comments in Figma, or a mix. Either works as long as feedback comes back within a reasonable window so the work doesn't stall.

Understanding the product, mapping the flows that matter, and putting one key screen into two or three visual directions. By the end of it you're looking at real design, not a research deck.

Often. Picking up someone else's Figma, cleaning up components, and pushing the visual layer forward without rebuilding from scratch is a normal part of the job.

For products: activation, onboarding completion, task success, retention. For websites: conversion, whatever the primary action is. We agree on the number before starting so there's nothing to argue about later.

I design them and interpret the results. Running them needs your analytics and dev setup, but structuring a test properly is a design problem as much as a technical one, and that's what I did daily at Spiralyze.

Figma files with organized components, documented states, an interactive prototype where useful, and handoff specs. All of it yours.

Yes. I review the built version against the design, and stay available for adjustments once real users arrive.