Mika Engineering

Web development for designers & agencies

You finished the design. Here’s exactly what happens next.

I turn your Figma, XD or Sketch files into custom website code. No WordPress, no page builder, no theme, no plugins. Your client owns every line and can take it to any host or developer.

One developer in Schwerte, Germany. Answers usually the same day.

One project, start to finish

  1. 01You send the fileDesign, notes, deadline
  2. 02I check it before buildingGaps and missing states flagged
  3. 03First page as the patternOn your private preview URL
  4. 04Every page and stateHover, error, empty, mobile
  5. 05HandoverLive site or files, plus editor access
  • Custom codeBuilt from your file, not squeezed into a theme.
  • Client owns itAll source code, no subscription, no lock-in.
  • Optional editorA lightweight CMS for texts, images and pages.
  • Small on purposeI take on projects that fit, and say so when one doesn’t.

The process

The journey of one project

Handing a design to a developer shouldn’t feel like a leap of faith. At every stage you know what you’re doing, what I’m doing, and what you’ll be able to look at.

  1. Stage 1

    You send the file

    [duration: …]

    You

    Share the Figma, XD or Sketch file, plus whatever you already know: pages, content status, deadline, where it should be hosted.

    Me

    Read through it, ask what’s unclear, and tell you honestly whether it’s a project I’m the right fit for.

    You see

    A reply, usually the same day, with a clear yes or no and the next step.

  2. Stage 2

    I check the design before building

    [duration: …]

    You

    Answer the open questions, or decide together with me how a missing piece should behave.

    Me

    Go through every frame for gaps: missing states, unclear breakpoints, components that behave differently on two pages.

    You see

    A list of missing states and questions, before any code exists.

    • Contact form: no error state designed
    • Team grid: what happens at 7 people?
    • Nav between tablet and desktop
  3. Stage 3

    The first page, built as the pattern

    [duration: …]

    You

    Review it on real devices and mark anything that doesn’t match your file. This is the moment to adjust direction.

    Me

    Build one representative page completely: type, spacing, components, breakpoints. It sets the pattern for the rest.

    You see

    The first page on your private, password-protected preview URL.

  4. Stage 4

    The rest of the pages, and every state

    [duration: …]

    You

    Check progress whenever it suits you. Collect feedback in one place, so nothing gets lost between emails.

    Me

    Build the remaining templates and the states in between: hover, focus, error, empty, loading, and every breakpoint.

    You see

    Every page, with hover, error and empty states, growing on the same preview URL.

  5. Stage 5

    Handover, and your client is live

    [duration: …]

    You

    Give the final go-ahead and tell me where it goes: your client’s hosting, yours, or a hosting agreement with me.

    Me

    Upload the site or package the files, set up editor accounts if needed, and walk your client through the editor.

    You see

    The files or the live site, plus editor access for your client.

Deliverables

What goes in, what comes out

No surprises at either end. If something on the left is missing, that’s fine; stage 2 is where we fill the gaps.

What I need from you

To start, and to get the build right.

  • The design file in Figma, XD or Sketch, with view access to all pages.
  • Desktop and mobile frames for the key pages, or a note on how it should adapt.
  • Fonts and licences for web use, plus image and icon files.
  • Content, final or placeholder, and who will edit it later.
  • Forms and functions: where enquiries go, uploads, languages.
  • Hosting plan: your client’s, yours, or a separate agreement with me.

What you get back

At handover, and yours to keep.

  • The website, uploaded to the agreed hosting or delivered as files.
  • All source code, owned by your client. Any host, any developer.
  • Every page and state from your file, on every breakpoint.
  • Editor access with personal accounts and 2-factor login, if you chose the editor.
  • A short walkthrough so your client can edit without calling anyone.
  • No subscription. Hosting and maintenance only if you want them.

Optional

An editor your client can actually use

If your client needs to change things after launch, I add my own lightweight editor. Not WordPress, and no monthly fee.

  • Visual block editor for texts, images and pages
  • Versions and undo, so mistakes are cheap
  • Personal accounts with 2-factor login
  • Separate layout tweaks for mobile and desktop

Hosting and maintenance are a separate agreement if you want them. Your client’s own hosting is fine too.

Your client edits content in place. Your design stays as you built it.

Built this way

Recent projects

Industry · Editor

Machine shop website

Page templates, the editor, and an enquiry form with technical drawing upload.

Education · DE / EN

Training academy website

Bilingual site in German and English, with the editor for the team.

FAQ

Questions designers ask

Anything else, just ask. I’d rather answer before the project than during it.

[quote from a designer]
[name, studio]

Will it match my file?

That’s the point. Your spacing, type and components are built as designed, and the first page is a checkpoint: you compare it to your file on real devices before I build the rest.

What if my design has gaps?

Most do, and that’s normal. In stage 2 I list missing states and open questions before writing any code. You decide, or we decide together, so nothing gets improvised silently.

Can my client edit it?

Yes, with the optional editor: texts, images and pages in a visual block editor, with versions, undo and 2-factor login. If they don’t need it, the site stays plain code.

Who hosts it?

Whoever you like. I can upload it to your client’s hosting or yours, deliver the files, or host and maintain it under a separate agreement.

What does it cost, and how fast is it?

[price from …]. [how quotes work, e.g. after stage 2]

I build mostly in the evenings and at weekends, so I plan timelines honestly up front rather than promising a rush.

Stage 1 starts here

Send the file. I’ll tell you what happens next.

A link to the design and a few lines about the project are enough. You’ll usually hear back the same day.

hello@mika-engineering.com