# mintel.me relaunch concept: freelance engineer site

Scope: this website only. Goal: a visitor understands what I sell within 10 seconds and
books a 20-minute intro call within 2 minutes. Low sales overhead, more bookable hours.

## 1. Positioning

**The senior engineer who makes AI-built software dependable.**

"Senior engineer for teams that build fast with AI and don't want chaos. Strong in design and frontend, provably clean in architecture and tests. Remote, booked in weekly capacity blocks."

- Headline candidate: "AI makes code cheap. I make it correct."
- Do not say: "everything", "fullstack for anyone", "vibe coding". Web3 is one specialty, not the identity.
- Language: English primary (international and Web3 clients), German route `/de` for DACH.

### Audiences (priority order)

1. Startups and founders (DACH/EU) who built with AI and now need it stable and extended.
2. Agencies with overflow capacity (recurring blocks; my team-lead and agency background is the argument).
3. Web3 teams (frontends, dashboards, wallet flows, WebSockets).

### What I offer / do not offer

- Offer: websites and web apps (Next.js/TypeScript, strong design), light backend (APIs, auth, integrations), CLI tools and automation, AI agents/MCP servers, architecture and code review, the spec/test/mutation process for teams, Web3 frontends. macOS apps on request only.
- Do not offer (state it plainly): Windows apps, mobile apps, running client infrastructure, database-heavy work, email/DNS administration.

## 2. Differentiator: verified AI speed

Anyone can generate code. The scarce thing is code that survives production.
Spec first -> red -> green -> refactor -> mutation check on changed code -> coverage as gap finder -> a delivery report with exact commands and results on every PR.

Site treatment:

- "How I ship" on the homepage plus `/process` with one real example report ("N cases, N mutants caught, changed lines X%").
- A downloadable sample delivery report.
- Evidence uses measured numbers only. Never claim: "100% coverage" (flash-loans measures 87.5%), "property-tested" (none found), or mutation scores that have not been run in full.

## 3. Site structure (4 items)

`Notes · Process · About · Book`

1. **/** Hero (headline, availability line, CTA) -> proof strip (key numbers, live references) -> How I ship -> offers and blocks -> stack -> CTA.
2. **/notes** Evergreen engineering write-ups, no client projects, no strategy IP. Candidates: the gate pipeline (spec, mutation, coverage ratchet), functional core and imperative shell (from the liquidation system), concept-to-code mapping (from the trading engine). Each with a diagram.
3. **/process** How I ship and the sample report.
4. **/about** Short story: 15 years in web (apprenticeship 2011), senior roles, frontend team lead at an agency, remote since 2021, own product business. 3-4 employer names at most, full CV as PDF. Be honest about the path: Vue/JS roots, today TypeScript, Rust, Solidity.
5. **/book** Cal.com embed, 20-minute intro call, email plus project description required.

References: one line on the homepage with live links (klz-cables.com, e-tib.com), no case-study pages. Naming both clients is cleared by the owner.
Remove: `/websites` page, the fixed-price configurator, RevenueLossCalculator, SMB-focused copy. Keep `/blog` out of the nav.

## 4. Design

- Dark, technical, one accent color (green), mono for technical elements, Inter for body.
- Keep the binary/blueprint idea from the current site as a very quiet background (reuse `BinaryStream`, `AbstractCircuit`).
- The delivery report block as a terminal-style card in the first screen is the centerpiece.
- Availability line fed by one constant (next free block, hours per week). Reuse `Availability.tsx`.
- Mockup of the hero was shown in chat; text/numbers in it are placeholders.

## 5. Offers and pricing

### Capacity blocks (main offer)

| Block     | Per week | Per month | Rate                           |
| :-------- | :------- | :-------- | :----------------------------- |
| Focus     | 15 h     | 60 h      | 100 EUR/h -> 6,000 EUR         |
| Half-time | 20 h     | 80 h      | 100 EUR/h -> 8,000 EUR         |
| Full-time | 35-40 h  | 140-160 h | 100 EUR/h -> 14,000-16,000 EUR |

Rate: 100 EUR/h, decided. DACH freelancer average is about 103 EUR/h (freelancermap Freelancer-Kompass 2026), senior developers list 85-120 EUR/h. Raise it for new clients once blocks are booked out for 4+ weeks. Show monthly block prices on the site, not the hourly rate. 2-week notice, simple SOW, transparent time tracking.

### Entry offer: AI-code rescue (1 week, 35 h)

Audit of an AI-built codebase, test foundation, mutation baseline, prioritized report. Easy to buy, converts into a block.

### Website sprint plus subscription (for clients who want zero involvement)

- Sprint: time-boxed package (example 40 h, 3,800 EUR) with a clear scope list. Extra work is a follow-up block, not open scope. 50% at start, 50% at launch.
- Site: static Next.js, no CMS, no server, no database.
- Hosting: managed platform (Cloudflare Pages or Vercel) in my account, flat monthly subscription (example 49-99 EUR) including hosting, SSL, domain renewal at cost, 1 h of changes per month. Deployment: git push builds automatically, client approves via a preview URL by email.
- Changes: by email or message, no CMS training.
- Domain: client is the registrant; transfer-out and source handover on request.
- **Email and DNS are out of scope.** Never switch nameservers. Only the two records `A/CNAME` for apex and `www` are changed, after exporting the existing records, and mail delivery is checked afterwards. Mailboxes stay with the client's provider.
- No SLA, no on-call; changes within 2 business days. Cap the number of subscription clients (for example 10) to protect bookable hours.
- Open decision: offer the subscription, or only handover plus 14 days of bug fixes.

## 6. Getting clients (low effort first)

1. Own network: former colleagues from i22, Trusted Shops, sdox.io, Sevenval. Ten personal messages.
2. LinkedIn and X: one post a week from real work (process, numbers, diagrams), one pinned "next free block" post.
3. Platforms (freelancermap, freelance.de, Web3 job boards) as a secondary channel.
4. Direct outreach: 10 targeted messages a week with one template.
5. Testimonials: one line each from existing clients.

## 7. Proof usable on the site (measured facts only)

- Liquidation system: 7 chains, Rust plus Solidity, 1,339 commits since 2026-09-16, 6,365 test markers, mutation gate with zero-survivor policy, coverage ratchet (badge 87.5%). Revenue to date is 0 EUR; show engineering and architecture only, no profit claims, no strategy details.
- Trading engine: spec-first structure, functional-style gates with self-test.
- Live references: klz-cables.com, e-tib.com.
- Still to measure before quoting: full mutation run and real coverage on the main system.

## 8. Risks for the site itself

- This repo currently has no tests and tracked tmp/log files in the root. The rigor pitch needs a tested site: spec tests for availability logic, booking flow and redirects, plus a CI gate.
- Impressum needs a serviceable address (DDG section 5); settle it with a tax advisor. Do not publish tax, visa or payment-provider details.
- Scheinselbststaendigkeit: prefer 15-20 h blocks over one client at 35-40 h.

## 9. Implementation order

1. Cal.com event and `/book`.
2. Spec tests for availability and redirects, then new hero, nav and offers; remove old SMB sections.
3. `/process` with the sample report.
4. First two notes with diagrams.
5. English copy pass, then `/de`; SEO/OG basics; redirect `/websites` to `/`.