iC iCoding
ENDE
Email directly

Start a project · iCoding

Tell me what should become clearer, faster or more stable.

Choose the closest entry point and send a short structured email. A clear first message makes it easier to estimate scope, risks and the most useful next step.

[email protected] See what to prepare
01

Website, SEO or WordPress

For new sites, landing pages, WordPress care, SEO foundations, performance and conversion improvements.

 02

Servers, hosting or Proxmox

For Linux, VPS/root servers, Proxmox, VPN, monitoring, CloudPanel, Nginx, migrations and hardening.

 03

Automation, AI or workflows

For n8n-style workflows, reports, API connections, content automation, AI-assisted processes and custom dashboards.

What to include

Helpful details: existing URL or server setup, current problem, desired outcome, timeline, budget range if known, and whether this is a one-time build or ongoing care.

Project brief

A few precise details beat a long first call.

You do not need a finished specification. The goal is to separate what is known, what is risky and what should be decided first.

01

Current situation

  • Existing URL, server, stack or provider
  • What already works and what does not
  • Known access limits, deadlines or dependencies
02

Target outcome

  • More inquiries, safer operation or cleaner workflows
  • Must-have functions versus nice-to-have ideas
  • Whether this is a one-time build or ongoing care
03

Next decision

  • Audit first, build first or stabilize first
  • Estimated urgency and preferred timeline
  • Budget range if one already exists
Fastest route

Send the rough version — I will help turn it into a realistic scope.

A short, honest message is enough. The first reply can clarify missing information, risks and the most useful starting point.

Send a prepared brief

After the first message

A clear request turns into a calm, realistic next step.

The first reply should reduce uncertainty: what is possible now, what needs checking and which route avoids unnecessary work.

01

Scope triage

I separate the request into goal, current setup, risks and missing information — so the first decision is based on facts instead of assumptions.

02

Useful starting point

Depending on the situation, the first step can be an audit, a technical stabilization, a focused build or a structured concept before implementation.

03

Build or care path

If the fit is clear, the project can move into implementation, migration, optimization or ongoing care with clean responsibilities and checkpoints.

Before launch

The last step needs real-world details, not placeholders.

The site can be prepared technically, but publication should only happen after domain, legal and contact details are confirmed.

01

Domain & hosting

Final domain, host, DNS access, SSL decision and whether the site runs as static hosting, PHP hosting or later CMS.

02

Legal data

Real operator name, privacy details, tools used and legal review before public launch. A public postal address is not required according to the operator’s country.

03

Contact & tracking

Final email inbox, optional form handling, spam protection and a decision on privacy-friendly analytics.