Services
Systems, data models, and connections that form the backbone of your organization. Robustly built, logically designed and future-proof in use.
AI
A controlled layer between AI and your systems. Safe context, logging, permissions, and data access under full control.
More about MCP →Database engineering
Data models, indexing, and query optimization for stable applications with scalable performance and reliable reporting.
More about Database engineering →Mobile payments & offline sales
One sales stream for online and physical transactions. Integration with terminals and automatic synchronization with inventory and finances.
More about Payments →Reservation & ticket systems
Availability, planning, capacity, and payments in one system. Complete automation of reservations and check-ins.
More about Reservation Systems →Cash registers
Transaction platforms linked to inventory, accounting, and webshop. Fast, stable, and usable in complex workflows.
More about Cash Register Systems →Multilingualism
Multilingual structure without copying and pasting. One source model, consistent URLs, translation flows, and publication control.
More about Multilingualism →Webshops
Fast, scalable webshops that connect directly to inventory, prices, customers, and data streams. Frontend on a robust backend.
More about Webshops →Websites
Technical, fast frontends that logically connect to your systems. Multilingual, secure, and built on solid foundations.
More about Websites →Support
Workflow and support system for customer inquiries. Automatic triage, contextual replies, and integration with internal systems.
More about support →AI
AI is only valuable when it is safe, controllable, and usable within your processes. We build AI applications that integrate with your existing systems, with clear boundaries: which data may be used, which actions are permitted, and what must always remain traceable.
Where AI delivers the most
- Work faster with files, documents, and knowledge (searching, summarizing, concepts).
- Automatic triage and routing of questions, tickets, and workflows.
- Analysis of operational data: deviations, trends, and causes.
- Assistants can collaborate in existing tools, without extra systems.
What we always guarantee
- Data access is explicit and limited.
- Complete logging and audit trails per query and action.
- Security by design: authentication, authorization, and rate-limiting.
- Human-in-the-loop where actions have impact.
Technical deliverables
- Inventory of use cases, risks, and data flows.
- Design of AI architecture: context layer, tools and guardrails.
- Context unlocking (RAG/search layer) on documents or databases.
- Tooling for actions with limited privileges.
- Integrations via APIs, webhooks, and events.
- Monitoring of quality, latency, costs, and error behavior.
- Safe test and acceptance environment.
Use cases
AI triage for support and workflows
Operational analysis with controlled data
Stability, safety, and further development
AI solutions remain reliable only if permissions, logging, and integrations stay up to date. With the management package, we monitor stability and security. Extensions and new use cases fall under further development.
FAQ
How do you prevent AI from seeing or doing too much?
With a controlled tool and context layer. AI only has access to explicitly permitted resources and actions, everything is logged.
Where is this happening and what does it mean for privacy?
Where possible within your infrastructure or an agreed private environment. Data does not leave the domain without explicit choices.
How do we ensure the quality of the output?
Through fixed guardrails, evaluation on example cases and monitoring. For critical flows, human review is standard.
Is this scalable to multiple teams or systems?
Yes. Once the foundation is in place, use cases can be added in a controlled manner without instability elsewhere.
Data
Data is at the core of every system: the data model, the database, and the management layer that works on it. We combine database engineering and custom backoffice/CMS into one consistent data layer that is fast, remains scalable, and is accurate across all channels.
When this is necessary
- Increased complexity hinders performance and scalability.
- A generic CMS hinders management and workflow.
- Multiple systems use the same data without a clear truth.
- AI, dashboards of automation require reliable datasets.
What it yields
- One source of truth for websites, webshops, portals, and APIs.
- Fast and predictable queries, even under growth.
- Clear management flows with roles, rights, and logging.
- A foundation that remains expandable without new complexity.
Technical deliverables
- Design or redesign of the data model.
- Indexing, query optimization, and database tuning.
- Cleaning, migration, and consolidation of data.
- Custom CMS/backoffice around your data model.
- Role and rights structure with audit trails.
- API layer for frontends and integrations.
- Monitoring of performance and error behavior.
Use cases
Headless data layer for website and app
Restructuring of growth system
Multilingual content model with governance
Data does not stay healthy on its own
Growth changes workloads, data flows, and management processes. With management we monitor stability and security. Expansions and restructurings fall under further development.
FAQ
When is optimization enough and when is redesign needed?
We determine that based on the analysis of queries, tables, data quality, and growth paths.
How do you migrate without downtime?
Phased, with parallel structures, synchronization, and a controlled switch-over moment including a rollback plan.
How do you ensure data quality?
With constraints, referential integrity, validation rules, and management flows that prevent errors instead of correcting them.
Is this suitable for dashboards and AI?
Yes. Reliable reporting and safe AI start with one clear data model and verifiable changes.
Who owns data and code?
You. Data, schemas, and project-specific code remain the sole property of your organization.
Mobile payments & offline sales
An extension module for situations where you want to sell outside the fixed counter: events, pop-up locations, trade shows, or seasonal sales. Transactions remain part of the same inventory and revenue stream.
When this is relevant
- Sales at varying locations (market, fair, outdoor location).
- Seasonal shops or temporary stands next to a permanent store.
- Salespeople in the store who process mobile payments (e.g. reducing queues).
- Situations where the internet is unreliable and offline transactions are needed.
What it yields
- One source of truth for revenue, inventory, and reporting.
- Direct processing in the cash register system as soon as the connection is available.
- No manual post-corrections of transactions or inventory.
- Low technical overhead: mobile device → terminal → system.
Technical deliverables
- Mobile transaction flow linked to the existing cash register system.
- Optional integration with terminals such as SumUp or other API-based providers.
- Offline-first design: transactions are buffered and automatically synchronized.
- Correct inventory changes and sales registration in the same data stream as the store.
- Role and rights management for mobile users.
- Reporting on one side: no separate systems, no duplicate data.
Use cases
Event sales for existing store
Pop-up location with changing connection
Store employees with mobile payment module
Maintenance & further development
For mobile sales, stability is of great importance. With the management package, we monitor data flows, synchronization, and terminal connections. Structural expansions or new payment providers fall under the further development package.
FAQ
Does this work without internet?
Yes. Offline-first transactions are held locally and synchronized as soon as possible.
Is SumUp mandatory?
No. SumUp is an option. Other terminals can be integrated via API.
Are transactions processed differently than in the store?
No. All sales streams come together in the same system, data model, and reports.
Can multiple devices be used at the same time?
Yes. Each device has its own session, but works against the same system.
Reservation & ticket systems
Systems for planning, availability, capacity, and payments. Fully tailored to your operational process, without reliance on generic SaaS tools.
Process challenges
- Double bookings or uncertainty about availability.
- Manual planning or overlapping schedules.
- Different channels (phone, website, counter) that do not synchronize.
- No insight into occupancy, capacity, and no-shows.
What you win
- One system that manages all reservations and tickets.
- Automatic confirmations, reminders, and payments.
- Real-time insight into capacity, planning, and expected visitors.
- Flexible expansion for multiple locations or resources.
Technical deliverables
- Data model for reservations, time slots, resources, capacity, and status.
- Backend modules for scheduling, modifying, canceling, and no-shows.
- Front-end reservation module (standalone, website or app integration).
- Calendar links (Google / Outlook) where relevant.
- Stripe/Mollie payments with automatic settlement.
- Dashboard for management and check-in (check-in, scanning).
- Multilingual options for international or tourist audiences.
- Logging, auditing, and role management for teams.
Use cases
Self check-in for small-scale hospitality
Time slot reservations for busy locations
Ticketing + scanning for events
Continuity & optimization
Operational systems require stability. With the management we monitor availability and performance. Changes in flows or expansions to additional locations or resources fall under the service package Development.
FAQ
Can customers also pay when reserving?
Yes. Stripe or Mollie integration is possible, including refunds and no-show logic.
Can multiple locations be in one system?
Yes. The data model supports locations, resources, and teams.
Is this a replacement for commercial SaaS?
Yes, when standard tools fall short in process logic, multilingualism, rates, or integrations.
What about security?
User roles, logging, audit trails, and secure connections are standard components of the system.
Cash registers
Cash platforms for physical stores: fast transaction processing, accurate inventory changes, and a stable connection with your administration and any webshop. Robust, predictable, and built on your processes.
Operational needs
- Reliable cash registers that respond immediately, even during peak times.
- Product, price, and inventory management that is always accurate.
- Clear data for physical store and, if available, webshop.
- Ready for expansions such as gift vouchers, customer cards, employee rights, or multiple counters.
Core result
- Quick and error-free checkout at the counter.
- Always accurate inventory levels, regardless of volume or time.
- Consistent administration without duplicate work or loose spreadsheets.
- Possibility to expand to mobile sales or webshop integration.
Technical deliverables
- Complete cash register system tailored to your assortment and workflow.
- Data model for products, variants, prices, VAT, and inventory movements.
- Link with accounting for accurate revenue and daily reports.
- Optional connection with webshop (inventory, orders, prices).
- Rights structure for employees (roles, security, logging).
- Reports: revenue, product performance, margins, and inventory changes.
- Integration option with mobile sales and terminals like SumUp (upsell).
Use cases
Physical store with inventory connection
Store with multiple counters
Webshop as an additional sales channel
Long-term stability
Cash systems must always work. With continuous management we monitor performance, data flows, security, and updates. Larger expansions, additional reports, or new modules are addressed in phases within the development package.
FAQ
Do you support multiple counters or branches?
Yes. All cash registers operate on the same dataset with consistent prices and stock levels.
Can existing pin terminals be connected?
Yes. Most terminals are connectable. SumUp can optionally be integrated for mobile sales.
Can the system process webshop mutations in addition to physical ones?
Yes. The inventory and revenue are processed centrally for a complete data stream.
How are reports structured?
Based on your data model: revenue, products, margins, daily totals, and inventory movements.
Who owns the data?
You. All data, including project-specific code, remains completely yours.
Multilingualism & content architecture
Multilingualism is not a "translation," but architecture. We design content structures in which languages, URLs, metadata, and publication flows work together logically, so your organization can scale without duplication or management chaos.
When this is necessary
- Your site or platform is growing internationally (multiple languages, countries, or markets).
- Translations must remain manageable without copying and pasting.
- SEO/URL structure must be consistent and verifiable per language.
- Content should have one source of truth, with variants per language.
What you win
- One data model for content with clear language variants and relationships.
- Fewer errors due to central structure, no loose duplicates.
- SEO-pure language routes and consistent metadata per language.
- Faster publication and clear responsibility within the team.
Technical deliverables
- Content model with source content and translation variants (relationships, fallback strategy).
- URL strategy per language (prefix/subdomain where applicable) and routing rules.
- Metadata structure per language (titles, descriptions, slugs, open graph).
- Workflow: concept, review, translation, publication and sync of updates.
- Tools for editing: status, missing translations, consistency checks.
- API output per language for website, apps or external channels.
- Migration plan for existing content (old structures to new model).
Use cases
Website with NL/EN and SEO-pure structure
Product content multilingual via CMS
International content governance
Long-term consistency
Multilingualism requires discipline and maintenance. With management we monitor stability, performance, and updates. Expansions such as additional languages, new content types, or workflow adjustments fall under further development.
FAQ
Is this only for websites?
No. The same structure also feeds webshops, apps, portals, and APIs.
Can we add languages later?
Yes. If the data model is set up correctly, expanding to additional languages is predictable and manageable.
How does fallback work when a translation is missing?
We design a clear fallback strategy (e.g. displaying source content) without inconsistent behavior.
What is the difference with "just translating"?
Translation is content. Multilingualism is structure, workflow, URLs, and governance that keeps everything consistent.
Webshops
Webshops built as part of your system architecture: fast, scalable, and connected to inventory, prices, transactions, and internal processes. Not a separate module, but a solid backend with an efficient frontend.
When this is necessary
- Your stock or prices come from another system.
- Your webshop must work in real-time with the cash register, ERP, or administration.
- Standard platforms like Shopify or WooCommerce impose too many restrictions.
- You want full control over performance, data, and extensions.
What you get
- Fast, stable webshop that continues to perform under peak load.
- Complete control over data streams and data model.
- Seamless integration with physical store or cash register system.
- Multilingual options for international reach.
Technical deliverables
- Webshop backend with product, price, stock, and customer logic.
- Checkout module with Stripe/Mollie and order processing.
- Integrations with cash register system, ERP or accounting.
- Data model tailored to your product structure and variants.
- Multilingualism for frontend and product data.
- Optimizations for caching, performance, and scalability.
- Dashboard for orders, customers, deliveries, and reports.
Use cases
B2B portal with customer-specific prices
D2C webshop linked to physical store
International platform with multilingualism
Continuity for sales
Webshops must keep running. With the management package, we monitor performance, security, and uptime. For campaigns, new countries, or larger expansions, you use the development package.
FAQ
Which platforms do you use?
PhloShop as a basis: fast, scalable, and under the full control of your organization. Other platforms only if there is a clear reason.
Can it be linked to existing systems?
Yes. Inventory, prices, orders, and customer data can be integrated in real time.
How is management?
CMS of backoffice is being set up so that product and order management remains efficient.
Is multilingualism possible?
Yes. Both frontend and product data can be set up to be multilingual.
Websites
A website is not a standalone project, but the frontend of your system. Fast, technically strong, and directly connected to your CMS, webshop, reservations, or data platform.
When a Q-dev website makes sense
- Your system needs a reliable, fast, and secure frontend.
- Your content comes from a custom CMS or headless backend.
- Your website must function multilingual with central content logic.
- Performance, security, and data connections are more important than design tricks.
Core benefits
- Blazing fast loading times due to minimal overhead and server-side optimizations.
- Logical connection with backend systems (CMS, reservations, webshop, MCP).
- Multilingualism without content duplication or structuring.
- Full control: own hosting, own code, no lock-in.
Technical deliverables
- Frontend that works directly on your CMS or data structure.
- Routing, caching and performance optimizations at the system level.
- Integrations with reservations, webshop or MCP if available.
- Multilingualism (URL strategy, content sync, language-dependent logic).
- Security layers: headers, rate-limiting, input validation, session management.
- Basic reporting for visitors, behavior, and technical performance.
Use cases
Corporate site linked to headless CMS
Website + reservation module
Website as a gateway to the data platform
Stability after going live
A website that is part of a larger system requires technical stability. With a suitable service package 'Management' or 'Further Development', we keep performance, security, and uptime closely monitored. Adjustments to content or logic can be easily implemented later.
FAQ
Can you also take care of design?
The focus is on technology and performance. We can provide design in line with your wishes, but the emphasis is on a stable and fast technical foundation.
How does multilingualism work?
Content is centrally managed and published per language variant. No loose copies, but one consistent structure.
Is migration possible?
Yes. Old content structures are being migrated to a clear, future-proof model.
Can you connect with existing systems?
Yes. CMS, webshop, reservations, data feeds, and MCP can be integrated.
Support
After the go-live, the real use begins. Support at Q-dev is focused on continuity, clarity, and predictability: one point of contact for technical questions, incidents, and necessary adjustments within the agreed service frameworks.
What support entails
- Handling of technical questions and reports.
- Analysis and resolution of incidents within the system.
- Monitoring of stability, safety, and basic functionality.
- Alignment on priority and impact of issues.
What support is explicitly not
- No unlimited development or feature expansion.
- No ad-hoc changes outside agreed frameworks.
- No substantive or operational support for end users.
- No replacement of internal processes or decision-making.
Part of the service agreements
- One fixed technical point of contact.
- Registration and follow-up of reports.
- Classification by urgency and impact.
- Repair or workaround within reasonable timeframes.
- Feedback on the cause and measures taken.
- Documentation of relevant changes or findings.
Typical situations
Incident after update of external change
Questions about the operation or behavior of the system
Minor corrections within existing system
Connection with management and further development
Support is an independent service. Within the management package, the focus is on preventive stability, safety, and monitoring. Issues that require structural adjustment or expansion are addressed within further development, always in consultation and with a clear scope.
FAQ
How does a support ticket proceed?
Notifications are recorded, analyzed, and followed up based on urgency and impact, in accordance with the agreements in the service level agreement.
Is support reactive or also proactive?
Support is primarily reactive. Proactive monitoring and preventive measures fall under the management package.
Are changes applied automatically?
No. Structural changes or expansions are always coordinated and fall under further development.
Is there direct accessibility?
Accessibility and response times are defined in the service agreements and tailored to the type of system and its use.
Combined systems
The greatest profit arises when systems work together logically. We design and build integrated solutions in which the cash register system, webshop, CMS, reservations, MCP, or internal processes form one coherent whole.
Why combine?
- Fewer loose systems, fewer errors, less duplicate work.
- One data model that is consistent everywhere: inventory, prices, content, customer data.
- Better performance and predictable behavior.
- Future-proof foundation for growth or internationalization.
Typical combinations
- Cash register system + webshop + inventory logic.
- CMS + website + multilingualism + MCP layer.
- Reservations + ticketing + payment streams + dashboard.
- Internal data + AI via MCP for analysis or process support.
Architecture & technical deliverables
- Analysis of existing systems and data flows.
- Design of a future-proof system landscape.
- Data model harmonization (prices, inventory, content, customers, orders).
- API connections between modules or external systems.
- Performance optimization across multiple services.
- Security layers: authentication, authorization, logging, auditability.
- Phased migration, without disruption of daily processes.
Use cases
Retail: store + webshop + inventory
Hospitality: website + reservations + check-in
B2B: CMS + multilingualism + MCP for data access
Architecture that moves with you
Combined systems are never 'finished'. With ongoing technical service Management or Further Development, connections, datasets, and processes remain stable and secure. Expansions can be implemented in phases without disruption.
FAQ
Does everything need to be built at once?
No. Most projects are carried out in phases, without interrupting the operation.
Can existing systems continue to exist?
Yes. We link where possible, and replace only where necessary.
What is the advantage of a single data model?
Very large: fewer errors, faster reports, better performance, consistent behavior across all channels.
Can you also integrate AI (MCP)?
Yes. AI gets controlled access through tools, never to raw data.
Service & Continuity
Systems require stability, security, and timely updates. These packages form the foundation for long-term technical peace and predictable maintenance.
Management
For systems that need to run daily without surprises.
- Security patches & updates
- Security layers (headers, certificates)
- Monitoring of uptime & error messages
- Back-ups & recovery tests
- Basic response to incidents
- Stable technical foundation
Further development
For systems that need to grow in addition to stability.
- Including all Management components
- Fixed development capacity per month
- Small expansions & optimizations
- Technical alignment when needed
- Performance improvements
- Quick response to changes
Specific service needs?
For organizations with special requirements regarding continuity, privacy, or operational support, a separate custom package can be explored. This is not a standard offering and is tailored exclusively to individual needs.
Feel free to get in touch to discuss what is needed and whether this fits within your system and working method.