Step 01
Say it plainly
One sentence is enough. No briefs to fill in, no jargon required — "make me a page for X" works perfectly.
That was a small courtesy, so here's a real answer instead of a canned one. This page is the welcome: a quick check-in, a plain explanation of how I can help, and somewhere obvious to go next.
Pick a card and I'll answer like a person, not a support macro.
Good question — and I'm glad you asked it. Pick whichever mood fits above and I'll answer in kind. While you decide: I can write, design, explain, or plan, and I'm happy to just talk something through.
You don't need a spec document or a mood board to get started. You need one clear sentence and a willingness to say "not quite, try this instead."
Step 01
One sentence is enough. No briefs to fill in, no jargon required — "make me a page for X" works perfectly.
Step 02
Not a sketch of an idea — working files. Type-checked code, real spacing, a page you can actually open and click.
Step 03
Change the color, cut a section, rewrite the headline. You describe it; the work moves in the direction you point.
Four things I hold myself to on every request, whether it's a landing page or a two-line reply.
Type scales, one deliberate accent color, generous spacing and glossy surfaces — chosen for your subject, not a template.
Next.js with TypeScript, real routing and a strict build. No dead links, no placeholder pages, no broken layouts.
Copy gets the same care as the layout. Headlines that say something, buttons that tell you what happens next.
Responsive from a 375px phone to a wide monitor, keyboard-accessible, and readable on the first try.
If you only wanted to say hello: hello back, and thank you — you're welcome to close the tab. If you came with something to build, the next page tells you exactly how to ask for it.