← "Built" does not mean:
never look at it again

Built doesn't mean
ready forever.

Your website is up and running. Your forms are working. Perhaps there are also integrations and automations running behind the scenes.

But technology is constantly evolving. Software gets updated, tools change, and every now and then, something needs attention.

With Care, I remain technically involved in the system—through periodic maintenance, inspections, and support within the agreed-upon scope.

Ongoing Maintenance · Support · Technical Follow-up

You don't have to
keep track of
what needs
technical attention.

A website or automation system doesn't cease to exist once a project has been delivered.

Plugins receive updates. Licenses expire. Tools change. A link may break. An integration may behave differently after external software makes a change.

Not every technical issue is a disaster. But someone does need to notice it, look into it, and address it when necessary.

01

You don't want to check for yourself whether everything is up to date.

02

You want to know who to contact if you have a technical issue.

03

There are automations that may still require attention even after they have been implemented.

04

You don't want to have to start from scratch with minor technical details every time you begin a new project.

Not because something is bound to go wrong all the time.

Because, after all, technology requires maintenance.

I can build something.
And then disappear.

But that's not
how I want to work.

That's why my work doesn't necessarily end with the launch or delivery.

Would you like me to stay involved with the technical side of things? That's what Care is for.

Not a
“good luck with that,
see you later 👋”
handover.

Maintain.
Check.
Follow up.
Support.

Exactly what is covered under your Care plan depends on your technical setup and the plan you've chosen.

For example:

01

Website Maintenance

Updates, technical checks, and maintenance of the existing website.

02

Security & Backups

Monitoring of security and backups within the agreed-upon setup.

03

Licenses

Monitor relevant technical licenses and renew them as agreed.

04

Technical Inspections

Check to see if any parts of the existing setup need attention.

05

Minor changes

Minor technical adjustments that fall within the agreed-upon Care scope.

06

Automations

Periodically review and test existing agreed-upon workflows, as appropriate.

07

Support

A dedicated technical point of contact whenever an issue arises.

Not everything listed above is automatically included in every plan. Your Care-scope will be clearly agreed upon in advance.

How often I check,
you help decide.

Not every technical setup requires the same maintenance frequency.

That is why Care can run at different intervals.

01

Monthly

Maintenance · every month

For setups that require more frequent technical follow-up.

02

Quarterly

Maintenance · every 3 months

Periodic maintenance spread out over the year.

03

Semiannually

Maintenance · every 6 months

For setups where a lower maintenance frequency is appropriate.

04

Annually

Maintenance · every year

A scheduled annual technical maintenance check.

The selected period determines the maintenance frequency and runs for the agreed-upon subscription period.

We'll determine in advance which plan is right for your setup.

Not every technical
issue needs to
become a
new project.

A minor adjustment. A plugin that needs attention. A link that no longer works. A setting that needs to be changed.

Within Care, provisions can be made for minor technical changes within the agreed scope.

Small ≠ a disguised

redesign.
😌
redesign.
😌

New pages, major changes, new features, or new automations are not automatically covered by Care.

Is it a little bigger than the Care-scope? If so, I'll discuss it with you first.

“It worked when
we built it”
is not a
maintenance plan.

Automation depends on the systems it works with. And those systems don't necessarily stay the same.

Tools receive updates. APIs change. Fields are modified. Settings change.

That is why Care can also include periodic checks and tests of existing, agreed-upon automated processes.

Don't just fix it when something breaks.

Also check every now and then if it still does what we expect.

We specify which flows are monitored and how often within your Care scope.

Something's going on.
You know who
to email.

Maybe you know exactly what's going wrong. Maybe you just get an error message that makes no sense at all.

Go ahead and send them over.

01

Email

Preferred channel for technical support.

02

WhatsApp

Can also be used for quick support questions.

03

Call

Please make an appointment so that I can set aside time for it.

Standard support:
response within

2 business days.

Often sooner. But two business days is the timeframe you should expect with standard support.

← Unfortunately, sending one question through five channels doesn't make it five times faster

I don't just take over
someone else's
technical attic.

Was your website or technical setup built by someone else? If so, I'll take a look at what's there first before I add Care to it.

This is done through a paid technical audit.

After that audit, it may become clear that the foundation is perfectly usable, that some cleanup is needed first, or that a different approach makes more sense.

If you decide to continue working with me after that, the audit fee will be settled according to the agreed-upon terms.

First, I look at
what I'm taking over.

Only then do we agree on what
I'll be responsible for technically.

Care doesn't mean
everything is suddenly
“included.”

01

A new website or a major redesign?

02

New automation or expanded automation?

03

A minor technical change within your Care-scope?

04

Hosting?

05

24/7 technical help desk?

Care provides you with an agreed-upon level of technical support based on what is in place.

No unlimited pass for everything that has a plug.

And what about
that “AI”
in the name?

AI can be part of the technical systems and automation tools I work with.

But I'm not going to sell you AI support just because it looks good on a services page.

Exactly what this covers depends on the setup and is only included if it is actually part of what I maintain or support for you.

You run your business.
I'll keep an eye on
my part.

01

What's already there?

Did I build it? Then I already know the basics.

Is the setup provided by someone else? In that case, we'll start with a paid audit.

02

What does "Care" cover?

We determine which website, systems, automated processes, and technical components I will monitor.

03

How often do I check it?

Monthly, quarterly, semiannually, or annually—depending on your chosen Care plan.

04

I check the agreed-upon setup.

I'll perform the scheduled maintenance and inspections that fall within your Care scope.

05

Is something going on in the meantime?

Then you'll know where to go for technical support within your Care plan.

06

If something falls outside Care, I'll say so.

Will a request turn into a new project, a new workflow, or a major change? If so, we'll discuss it before I get started.

A few questions before
you let me adopt
your tech.

That depends on your technical setup and the plan you choose. We’ll clearly agree in advance on which website, systems, automations, and technical components I will maintain, monitor, or support.

Care can be billed monthly, quarterly, semi-annually, or annually. We'll determine the appropriate frequency in advance based on your setup.

The difference lies in the scheduled maintenance frequency: every month, every three months, every six months, or every year. No other differences in the formula are assumed beyond what we specifically agree upon.

That might be possible, but I'll first have a paid technical audit done to see what's there and what I can safely adopt.

Because I first need to understand the technical fundamentals, the systems used, and the existing options before I can take responsibility for my assigned portion of the project.

Minor technical adjustments may be covered under Care if they fall within the pre-agreed scope. New pages, major changes, new features, and new automations are not automatically included.

For standard support, I'll respond within two business days. I often respond sooner, but two business days is the timeframe you should expect.

No specific response time has been set for urgent support yet. Please email me with the details so I can review the situation within the terms of your plan.

That's possible if the agreed-upon automations fall within your Care scope. We'll determine in advance which flows I'll monitor and how often.

New or expanded automation is not automatically covered by Care. In that case, we treat it as a separate Flow Fix or another new scope.

No. Hosting is separate from Care. The specific hosting terms are set forth separately.

I can help track relevant technical licenses and, where agreed, renew them. We’ll determine in advance how licenses will be managed and billed.

AI may be part of the systems or automation processes that I maintain or support. What that means specifically will only be included if it truly pertains to your setup and the agreed-upon scope.

The selected maintenance period will run for the agreed-upon subscription period. The specific terms and conditions will be established in advance; I will not include any terms and conditions here that have not yet been determined.

You have enough
to keep track of.
Your plugins don't
need to be one of them.

Did I build your website or automation system, and would you like me to remain involved on the technical side? Or is there already a system in place, and are you looking for someone to take over maintenance and technical support?

Tell me what's already there. Then we'll first see what I can responsibly take on and which type of care would be appropriate for that.

A single point of contact for technical issues.
Clear agreements on what is covered.

Explore Care with me →

Let's see what it says first