
Pizzeria website. Self-initiated concept, not client work.
Kipinä & Varras
A Helsinki pizzeria: live opening status, a filterable menu, lunch offer and pickup ordering, in Finnish and English.
Independent developer in Helsinki, working directly with business owners.
Talk it through: hello@theopscrafter.com Book a 20-min call ↗
Kaarna is a salon website I designed. Book a sample appointment and watch it appear in the owner's calendar.
Choose a service and a sample time. The appointment lands in the owner's calendar below, as it would on a real booking site. Nothing is booked or sent.
The booking simulation needs JavaScript. You can still open the Kaarna concept and try its booking flow there.
Your sample appointment
That's the whole loop: the customer picks a time, and the owner sees it straight away. A real site would also confirm by email and send a reminder.
Open the full Kaarna concept ↗Run an office rather than a salon? See how an invoice gets checked automatically, or read about business websites and web apps and internal tools.
One supplier invoice, checked by code, suggested by AI and decided by a person. This one doesn't add up: step through it and see who catches the problem.
Interactive simulation with fictional data. No AI service is called and nothing is posted.
Totals mismatch. Net plus VAT is 677.70, but the invoice states 697.70. The totals check fails, the AI step is skipped, and the reviewer can only reject and return it.
Duplicate. The duplicate check finds the same supplier, number and amount received on 2 October. The AI step is skipped, approval is unavailable, and the reviewer can only reject and return it.
Valid invoice. All four code checks pass. The AI suggests account 4610 with confidence 0.86, stored separately. A reviewer approves or rejects. The record keeps the checks, the suggestion and the decision as separate fields. Nothing is posted.
The real version runs in a company's accounts payable team: Purchase Invoice OCR case study. More on integrations and office automation.
Five websites I designed on my own initiative for fictional Helsinki businesses. Each one shows a different kind of site and what a similar build would cost.

Pizzeria website. Self-initiated concept, not client work.
A Helsinki pizzeria: live opening status, a filterable menu, lunch offer and pickup ordering, in Finnish and English.

Hair salon website. Self-initiated concept, not client work.
A Helsinki hair studio: priced services, a before-and-after slider and three-step booking, in Finnish and English.

Plumbing and heating website. Self-initiated concept, not client work.
A one-van plumber: pick the fault, your postcode and the times that suit, and the day's route sets the arrival window. A live section drawing marks up the fault. In English and Finnish.

Vintage design shop website. Self-initiated concept, not client work.
A Helsinki vintage design shop: a collection filtered by category and decade, 48-hour reservations and a sell-to-us flow, in Finnish and English.
Ajokuntoisia klassikoita harjun laella
“Roadworthy classics on the ridge”, the museum concept's headlineFamily car museum website. Self-initiated concept, not client work.
A family car museum: a collection browsable by decade, object filters, café and visitor information, in Finnish and English.
Indicative one-time build costs. Final quote depends on scope. Hosting, domain, third-party subscriptions and any applicable VAT are additional. USD amounts are approximate, converted at the ECB reference rate of 30 Oct 2026 (€1 ≈ US$1.12); quotes are made in EUR or USD. Website concepts are self-initiated designs, not commissioned client work.
Two products of my own and a system built for a company: the problem, what I did, and what can be shown.
Product · SaaS platform
Live · in use by customers
No customer or usage figures are published.
Product · Web, mobile, desktop
Pre-handover
No user numbers or security assessment results are published.
System · Integration
Live · private, in customer use
No screenshots, company names or invoice data are shared.
For a salon, a shop, a museum, a founder or an operations team. Start with one piece, or connect them all.
Design and build of a fast, accessible site, with booking, enquiry or contact flows and content you can update yourself.
Web apps and internal tools with roles, permissions and audit history, and mobile capture where the work happens.
Email, documents, accounting and ERP connections, with duplicate-safe processing, retries and exceptions routed to a person.
Suggestions, drafts and summaries, with rules for anything involving money or identity and a record of what was approved.
AI suggests. Code checks. A person decides. The same goes for how I work with you.
We talk through the business, the process and what a good result looks like. You get an agreed scope in writing.
Screens and flows you can react to before anything is built.
Work in small steps, with a preview you can open at any time.
Testing across devices, accessibility checks, and the awkward cases. You get a list of what was tested.
Launch, plus documentation for whoever runs it next, with ownership and support agreed up front.
I'm The Ops Crafter, an independent developer and product builder in Helsinki. I've founded two products of my own: a bookkeeping platform for small businesses and accountants, and a heritage platform for Nordic families and heritage associations. I've also built a private invoice-automation pipeline for a company's accounts payable team.
You work directly with me from the first conversation to handover. I use AI-assisted development tools and review what they produce.
Tell me about your business and what you'd like to change. Email is the most reliable way to reach me. I'm in Helsinki, Finland (UTC+2) and welcome clients in Europe and North America; calls with North American clients are scheduled in your morning.
hello@theopscrafter.com“Write an email” opens your mail app with these headings filled in.