Websites · Software · AI · Visibility

01 · Build

Software, websites and apps that work.

I build websites, web apps and custom software for businesses – carefully planned, cleanly built and looked after beyond launch. You talk directly to the person who writes the code.

Discuss your projectView services ↓
AppsSoftwareWebsites
Approach

From first request to running system.

You see early on how the solution is structured, where the project stands and which decisions are coming up.

01Request

Goal, context, problem.

02Discover

Users, market, risks.

03Design

Architecture and scope.

04Build

Developed close to production.

05Test

Check and refine.

06Operate

Launch and growth.

Project types

From idea to plan.

Choose a project type to see the building blocks it usually involves and the timeframe you can expect.

Typical projects

What should be built?

Project typeWebsite or relaunch
FocusStructure, design and speed
Timeframe (guide)4–8 weeks
Request this project
01UX / Design
02Frontend
03CMS / Backend
04Hosting
Architecture

A system you can understand.

Every layer is traceable and documented – from the interface through data and integrations to hosting.

Structure

Everything fits together.

Interface, logic, data and integrations are aligned and cleanly separated, so each part can be extended or replaced later.

Technologies
FrontendNext.js / React / Vue
BackendLaravel / Node / FastAPI
DataPostgreSQL / MySQL / NoSQL
AIOpenAI / Claude / Agents
DeliveryDocker / CI/CD
InfrastructureHetzner / Cloudflare
Milestones

Short stages, visible results.

Each stage ends with something you can see and test. How long it takes depends on the scope and type of project.

Stage 1Concept

Goal and scope

Target picture, scope and technical guardrails are set.

Stage 2Prototype

First look

Flows, interface and structure become clickable and testable.

Stage 3Core features

First working version

The key features run under real conditions.

Stage 4Launch

Live and supported

Release, monitoring and a plan for the next steps.

Definition

What are web systems?

Web systems are websites and web applications planned as one coherent system: information architecture, components, performance, integrations and measurable conversion paths work together. That keeps the solution maintainable and lets it evolve in day-to-day operation.

Read more: Website mockups from the live browser – Why screenshot templates fail on login and responsive layouts – and how live-browser mockups help.

Services

What I build for you.

Select a service for details, typical use cases and technologies.

Service

Websites

Fast, accessible websites with a clear structure and a design that fits your brand.

Service

Web applications

Customer portals, dashboards and internal tools in the browser – with login, roles and a solid data foundation.

Service

Online shops

E-commerce with Shopify, Shopware or WooCommerce – from checkout to shipping.

Service

Headless CMS

Flexible content editing and a fast website – including relaunches from WordPress, TYPO3 or Contao.

Service

Performance

Short load times and strong Core Web Vitals – measured, not claimed.

Service

APIs & integrations

APIs and integrations that cleanly connect your existing systems.

01 · Build · Websites

Websites

A website is more than a digital brochure. I build it as a maintainable system: clear information architecture, reusable components, short load times and measurable paths to an enquiry.

I rely on server rendering (Astro, Next.js and others), accessible interfaces and a design that carries your brand and offer – rather than a template look. Your team can update content easily, and the code stays easy to maintain.

Suitable for company websites, marketing sites and product landing pages in the DACH region that plan for visibility in search engines and AI search (SEO/GEO) and later extensions from day one.

Suitable for
Company sitesLanding pagesRelaunchMultilingual
Technologies
Next.jsAstroReactTailwind
Scope of work
  • Server rendering (SSR/SSG) with strong Core Web Vitals
  • Accessible interface that leads to an enquiry
  • Easy to edit, with a headless CMS if needed
  • Structured data (Schema.org) for search and AI
  • Launch with monitoring and ongoing refinement
In short

A website or straight to a web application?

If content and enquiries are at the centre, a fast, server-rendered website is usually enough. As soon as logins, roles, dashboards or complex data flows come in, I plan a web application. We clarify this together at the start of the project.

Request a project →
01 · Build · Web applications

Web applications

Web applications bring productive work into the browser: portals, customer areas, dashboards, internal tools and SaaS interfaces with authentication, roles and robust data models.

I choose the stack by goal (e.g. Next.js/React or Vue), not by trend – with a focus on maintainability, clear interfaces and testability. As a PWA (installable web app) where offline use or an app-like feel adds real value.

Typical projects: customer portals, admin interfaces, data-driven tools and MVPs that are meant to grow.

Suitable for
PWASPASaaSDashboardsPortals
Technologies
Next.jsReactVueNodePostgres
Scope of work
  • Login, roles and protected areas
  • Connection to existing systems via APIs
  • PWA, SPA or SaaS – depending on use
  • Clean data models and traceable architecture
  • Regular releases with visible progress
In short

Do you also build internal tools, not just customer products?

Yes. Internal portals and operations tools often pay off fastest: the same quality standards, a clear scope and noticeably less effort day to day.

Request a project →
01 · Build · Online shops

Online shops

An online shop is a sales system: catalogue, checkout, payment, taxes, shipping logic and the connection to ERP and fulfilment – not just a theme.

Depending on requirements I use Shopify, Shopware or WooCommerce, with a headless storefront where speed and a custom shopping experience come first. I plan migrations and relaunches with data transfer and so that existing rankings are preserved.

The goal: a stable checkout, maintainable extensions and a shop that gets found.

Suitable for
ShopifyShopwareWooCommercePayments
Technologies
ShopifyShopwareWooHeadless
Scope of work
  • Shopify, Shopware or WooCommerce – chosen for good reasons
  • Payment, taxes, shipping and a smooth checkout
  • Connection to ERP, PIM, CRM and fulfilment
  • Optional headless storefront for speed and custom design
  • Relaunch with redirects and protected rankings
In short

Which shop system do you recommend?

It depends on your range, your team and the integrations you need. Shopify is often good for a fast start, Shopware for deeper processes in the DACH region, WooCommerce when WordPress is already in place and the budget fits. The decision is made in the concept phase.

Request a project →
01 · Build · Headless CMS

Headless CMS

A headless CMS separates editing from presentation: content is maintained in a structured way, and the website stays fast, flexible and usable across several channels.

I often migrate from classic systems such as WordPress, TYPO3 or Contao, keep the workflows that work and replace what slows down speed, security or visibility. Preview, roles and component models are part of the setup.

The result: your editors keep working as usual, and the frontend is modern – without being locked into a rigid theme.

Suitable for
ContentEditorialRelaunchMultichannel
Technologies
SanityPayloadWordPressTYPO3
Scope of work
  • Structured content models instead of page sprawl
  • Migration from WordPress, TYPO3 or Contao
  • Preview, roles and approval workflows
  • Free choice of frontend (Astro, Next.js, Vue …)
  • Content reusable for website, app and AI applications
In short

Do we have to switch CMS completely?

Not always. Sometimes a hybrid or a step-by-step switch is enough. When security, speed or flexibility suffer, headless is often the cleanest route. We clarify scope and risk beforehand.

Request a project →
01 · Build · Performance

Performance

Speed is product quality and a ranking factor. The Core Web Vitals – LCP (how fast the main content loads), INP (how quickly the page responds) and CLS (how stable the layout stays) – help decide whether visitors stay and whether you get found.

I measure with lab and real-user data, prioritise the bottlenecks (images, JavaScript, caching, CDN, third-party scripts) and document every improvement transparently.

As part of a development project or as a focused optimisation of an existing website.

Suitable for
LCPCore Web VitalsOfflineEdge
Technologies
CDNSSRWorkboxLighthouse
Scope of work
  • Core Web Vitals: diagnosis and priorities
  • Leaner images, fonts and JavaScript
  • Caching, CDN and fast server responses
  • Review of third-party scripts (tracking, widgets, tag manager)
  • Before/after documented with measurements
In short

Is a one-off optimisation enough?

A focused pass often brings the biggest jump. But a website only stays fast with clear performance limits in everyday work and ongoing monitoring – otherwise new features eat up the gains.

Request a project →
01 · Build · APIs & integrations

APIs & integrations

Integrations connect shop, CRM, ERP, CMS and internal tools into one system – without copy and paste and without shadow spreadsheets.

I design REST and webhook flows, authentication (OAuth, API keys), error handling and retry logic so that integrations can be monitored and maintained. I prefer to wrap existing legacy systems cleanly rather than replace everything at once.

A development project is often only finished when the data flows correctly – not as soon as the interface is live.

Suitable for
RESTGraphQLWebhooksAuth
Technologies
tRPCGraphQLREST
Scope of work
  • REST, webhooks and event-driven flows
  • Authentication, rate limits and retry strategies
  • Connection of CRM, ERP, CMS, payment provider and PIM
  • Monitoring and traceable logs
  • Documented interfaces between systems
In short

Can you connect to our existing ERP?

Usually yes – via existing APIs, middleware or export/import bridges. First I check the data model, access rights and risks, then I build the leanest stable integration.

Request a project →
Imping Labs

My own products in operation.

Alongside client work, I build and run my own software, some of it together with partners. It forces the same decisions I make for clients – and shows me every day what holds up in operation.

01 · Tracking

usertrax

Conversion tracking, channel attribution, A/B tests and feedback.

02 · Practice software

TheraTap

Practice software for animal therapists – records, billing and booking.

03 · Business card

EloCard

Digital business card with a QR code – capture contacts at events and follow up.

04 · AI decision support

expertPANEL

Three virtual experts discuss – a structured decision report.

05 · Rentals

Nebenkosten Butler

Service-charge statements from receipts and contracts.

06 · Controlling

steerlytics Cloud

Controlling, metrics and cloud analytics for running a business.

07 · Mockups

Webdm

Website mockups from the live browser – real devices, exact pixels.

08 · Tax deadlines

Tax Reminder

Reminders and overview for tax prepayments.

09 · Property search

Immolike

Collect property listings and track them through to a decision.

FAQ

Frequently asked questions

Who does imping.digital build websites and platforms for?

For businesses in the DACH region – from established SMEs to startups – that need a maintainable digital system: from company websites and portals to online shops and SaaS products.

Which technologies do you use for web systems?

Depending on the goal: Next.js, Astro, React, Vue, Laravel, Node, FastAPI, headless CMS, Shopify/Shopware, plus PostgreSQL, MySQL or NoSQL – with a focus on server rendering, fast load times and clean interfaces.

How long does a typical development project take?

It depends on the scope and type of project. Smaller websites can be live within a few weeks; platforms and relaunches take correspondingly longer. After the initial call you receive a realistic schedule and a clear quote.

Can you relaunch existing WordPress or TYPO3 sites?

Yes. I often migrate to a headless CMS or a modern server-rendered stack, keep the editorial workflows and improve speed, SEO and GEO in one go.

How do you measure success after launch?

Through Core Web Vitals, conversion paths, indexing and – where relevant – visibility in search engines and AI answers. Operation and further development are part of the project.

Plan.Build.Run.

Free initial call

Ready to start?

Tell me briefly what you want to build. In a free 30-minute initial call we work out which approach fits. Afterwards you receive a clear quote – the price depends on the scope and type of project.

Discuss your projectAbout me and my network →
Automate →Amplify →
Selection 0