Guide

Connecting website creation services with existing systems

Does everything need to be replaced for this? Usually not. What can be connected to an existing system landscape, where the limits are, and which part typically takes the longest.

Quote on request4 to 8 weeksAs of 2026
In short

For website creation services, in most cases nothing existing needs to be replaced: inventory management, CRM, calendar, accounting, or phone systems are connected via interfaces. What matters is whether the respective system has a documented interface — and the time-critical part is almost never the technology, but obtaining the access credentials.

01 — Integration

Connection with existing systems

The most common misconception is that everything needs to be new. In most cases, the existing system landscape remains in place, and website creation services build on top of it — through interfaces, not through replacement.

What gets connected in practice: ERP, CRM, calendar, accounting, phone system, newsletter system, website. What matters is whether the respective system has a documented interface. Where none exists, there's usually a workaround — but that costs effort and needs to be clarified up front, not discovered later.

The time-critical part is almost never the technical integration, but obtaining access credentials. Starting early here noticeably shortens the project timeline.

02 — Requirements

What you need for a website

  • A clearly defined trigger. Not “we should do something with AI,” but a process that demonstrably costs time or orders today.
  • Existing content or data. Website creation services work with what's there. The more complete the starting point, the shorter the setup.
  • Access to the systems involved. Whoever manages the credentials needs to be involved from the start — this is, in our experience, the most common cause of delays.
  • One decision-making contact person. One, not three.
  • Willingness to refine after launch. The first weeks in real operation show what was missing in the concept. That's normal and accounted for.

03 — Bottlenecks

What typically causes delays

  • Content and deliveries. By far the most common cause of delay. Text, images, price lists, access credentials — what's missing blocks progress.
  • Decisions. When it's unclear who approves, the project waits. A named contact person with decision-making authority noticeably shortens the timeline.
  • Access to third-party systems. Getting access to inventory management, phone systems, or CRM regularly takes longer than the integration itself.
  • Endless review rounds. Two correction rounds are normal, five are a sign that the goal wasn't clear at the start.

04 — Questions

Frequently asked questions

How long does it take?

Four to eight weeks is realistic if content and images arrive on time. The bottleneck is practically never development, but approval of texts and photos.

Are there subsidies?

For digitalization projects in Austria, there are several funding programs, such as KMU.DIGITAL (kmudigital.at) or the aws digitalization subsidy (aws.at). Whether your project currently qualifies, we check individually — the application must be approved before awarding the contract in any case.

Can we manage the site ourselves?

Yes. You maintain texts, images, and simple pages yourself. For structural changes you get in touch — or not, that's not a dependency we build.

What does a website cost in Austria?

There's no serious way to answer that as a flat rate — the market ranges are huge because a one-pager and a multilingual company site with twenty pages are completely different projects technically. What matters most is how much content has to be created from scratch — that's almost always the biggest line item, not the technology. Send us a quick note about what you have in mind, and you'll get a proposal that fits your scope.

Does our website have to be accessible?

Since 28 June 2025, the Accessibility Act (Barrierefreiheitsgesetz) applies in Austria. Mainly affected are online shops, bookings, e-ticketing, and banking services in consumer business; micro-enterprises are exempt for services. A pure information site generally doesn't fall under it — we still build to WCAG 2.1 AA because it makes the site better for everyone and the rules tend to get stricter.

What does ongoing operation cost?

Hosting, domain, updates, and backups are ongoing costs — how much depends on the size and requirements of the site, and we state that transparently in the quote. Anyone who skimps on that skimps until the first security incident.

WordPress or something else?

Depends on the case. WordPress makes sense when many people manage content and standard features are enough. Where speed, security, or custom functions matter, we build leaner. We don't recommend what we like building most, but what you can still operate in three years.

Next step

Initial assessment, no obligation.

Briefly describe what you need. You'll get an honest answer about what's realistic and what it will roughly cost.