Size & team
SMEs, typically 5–50 people. Owners or managers who decide themselves, without a six-month enterprise procurement cycle.
Practical digitisation for SMEs — connect and simplify, do not stack more tools. Here is who that fits, when another type of partner is better, and how you avoid getting trapped if you later need to leave.
Usually businesses without a heavy IT department that want one technical contact for website, integrations and AI — step by step, not a big bang.
SMEs, typically 5–50 people. Owners or managers who decide themselves, without a six-month enterprise procurement cycle.
Trade, services, recreation, beauty, B2B and local businesses in Drenthe, Overijssel and the NL/DE border region — or remote when the fit is right.
Messy tech stack: Excel, point SaaS tools, Zapier/Make, email tennis. You want one coherent system, or a website that finally matches how you work.
Fixed price upfront, direct contact (Andre), training at delivery, and willingness to map processes before anything is built.
Transparency beats a bad match. In these cases I would rather point you elsewhere.
Multi-year programmes, hundreds of users, heavy compliance chains, or comparisons with Valtech, Capgemini, Ordina or DEPT: that is enterprise-integrator territory.
Worldwide support SLAs, follow-the-sun teams or always-staffed critical systems need a different scale than a specialist SME studio.
Ads, brand campaigns, content calendars or social-first work: hire a marketing agency. I can still collaborate with them as the technical partner.
If Shopify, a template or an off-the-shelf tool already solves the problem well, I say so. Custom work is not a goal in itself.
Worrying about depending on one developer is fair. This is the exit and growth path.
After full payment you get usage rights to the delivered work and, where agreed in the proposal, the source code — so you are not stuck with one supplier. Generic libraries follow the terms.
Documentation, admin guidance and a clear technical structure are part of delivery — not knowledge locked in one person’s head.
Your team learns how it works, where the limits are and how normal changes are made. If you later move to another partner, I support a clean handover.
Hosting, APIs and third-party software are named upfront. Changes outside scope are agreed separately — no silent extra invoices.
You work directly with Andre as your fixed contact. At the same time you get documentation, training and — where agreed — source code, so maintenance or handover to another party remains possible.
Yes within SME bounds: modular extensions, integrations with existing tools, and cases like Jan Sok (webshop live, wider system phased) and VYBR!S (multi-tenant platform on AWS). No enterprise-scale promise without that kind of programme.
Often yes if you have no IT department and want processes mapped first. Sometimes no: marketing campaigns or pure enterprise programmes belong with specialists. We discuss that line openly.
Yes. ultimAItech does not replace a brand or campaign team. I build the technical layer and coordinate with existing partners.