Customers & jobs
Keep customer, appointment, job status, photos, notes and open actions with the right record.
Digital solutions for real workflows
Less admin chaos.
More time for good work.
WerkZ adapts to the business – not the other way around. Inquiries, jobs, appointments, time, photos, materials, approvals, analytics and billing can be connected where they genuinely reduce friction. Existing software can stay when it already works well.
No office PC required
Smartphone-only can be a valid starting point.
A solo business can use a separately hosted WerkZ web app/PWA from a phone. Teams can add desktop views, roles, locations and integrations later.
What WerkZ can connect
One core, optional building blocks.
Time & field work
Mobile time tracking, job-site documentation, GPS, voice and photos where the work happens.
Approvals & integrations
Connect existing systems and keep important or irreversible steps under human control.
Analytics & simulation
Use history, metrics and what-if scenarios to compare changes without modifying real operational data.
Price guidance
Implementation, operation and infrastructure are priced separately.
Solo, Team and Business describe the implementation scope, not different software products. The active modules and the deployment model are chosen after the pre-check.
WerkZ Solo
implementation from €490Managed operation from €79/month.
A focused start for one person. Depending on customisation, many Solo projects are closer to €790–1,490 one-time.
WerkZ Team
implementation from €1,490Managed operation from €179/month.
Shared workflows, mobile updates, permissions and handoffs. Typical projects are often around €1,990–3,990 one-time.
WerkZ Business
implementation from €2,490Managed operation from €349/month.
Multiple processes, permissions and integrations. Larger scopes often start around €3,490–7,500 or more.
Deployment is a separate decision: WerkZ can run as managed cloud, cloud plus a local connector, on suitable existing customer hardware, on a prepared WerkZ Box, or in a dedicated/on-premises environment. Existing infrastructure is checked before new hardware is proposed.
No artificial mandatory subscription: managed operation covers real hosting, updates, monitoring, backups and agreed support. Self-managed or handed-over deployments can use a separate maintenance model.
Practice references
Reusable ideas come from real hands-on projects.
WerkZ Time
A private mobile pilot produced practical patterns for time tracking, job-site documentation, GPS, voice, photos and end-of-day summaries.
Analysis & Simulation
A private analysis experiment evolved into a general concept for time series, rules, scenarios and later comparison against reality.
DeutschZ
An active DayZ community server with its own mods, events, story and ongoing development. Much of WerkZ's practical engineering approach grew out of that work.
Website vs product
This site explains WerkZ. Customer systems run separately.
Production customer data is not meant to live in marketing pages. A WerkZ solution is deployed as its own web app/PWA or customer instance with its own login, permissions and data boundaries.
Optional building blocks
One operational context, many possible functions.
Customers & inquiries
Contacts, callbacks, notes, history and new requests.
Jobs & appointments
Customer, site, date, status, responsibilities and open items.
Time & field work
Time tracking, job-site documentation, GPS, voice, photos and day summaries.
Materials & documents
Keep materials, additions, photos and files with the right operational record.
Billing preparation
Bring completed work, time and materials together for review or handoff to existing accounting software.
Approvals & notifications
Keep important actions under human control, with simplified management views or connected channels.
Long-term analytics
Use operational history to identify duration, utilisation, recurring issues and other relevant metrics.
Simulation
Test alternative rules or scenarios against history without changing real operational data.
Integrations & automation
Connect existing software through suitable APIs, OAuth, webhooks, import/export or deliberate manual handoffs.
Different work situations
The same system should not look the same to everyone.
Solo / smartphone
Large actions, little typing, no office PC requirement.
Field / installation
Assigned job, navigation, time, photo, voice, issue and completion – including offline buffering where required.
Workshop / factory
Simple workstation or terminal mode for start, finish, quantity, scan and issue reporting.
Office / management
More context, approvals, exceptions and analytics; management can be reduced to a few concrete decisions.
Analysis & simulation
A private experiment became a reusable architecture idea.
The principle is domain-neutral: events and snapshots feed metrics; versioned rules create scenarios; simulation runs remain separate from real data; later results can be compared with reality. No private financial data needs to be exposed to customers for that concept to be useful.
Scope, not separate products
What Solo, Team and Business mean in practice.
Only the building blocks needed for the agreed workflow are configured. A phone can be enough for Solo; the same underlying records can later serve field staff, office and management.
Solo
Customers and inquiries, jobs, time and evidence in a focused personal workflow. Managed cloud is the simple default; suitable existing customer hardware can be assessed when needed.
Team
Shared jobs, mobile and office views, responsibilities, handoffs and approvals. Cloud, hybrid connection or a suitable local WerkZ Box are deployment choices separate from the function scope.
Business
Multiple processes, organisational boundaries, differentiated permissions, integrations, management decisions and audit. Infrastructure and processes are assessed before a specific setup is promised.
Industry offer
WERKZ – SCHROTTIES
The German standard offer for small scrap dealers and metal collectors describes a phone-first workflow for jobs, pickups, vehicle load, receipts, dealer prices, day-end and monthly preparation. The published standard price is €399 one-time plus €79/month for that defined version, including ongoing operation and updates. Check the exact live scope and device acceptance before a customer commitment.
Price boundaries
What the starting prices include – and what is separate.
The published “from” setup prices apply to clearly scoped configurations of existing WerkZ building blocks. Data migration, specialist connectors, new custom features and special infrastructure are quoted separately. Managed operation covers hosting, updates, monitoring, backups and agreed support; a technically suitable customer-operated handover may instead use a separate maintenance model.
German infrastructure guidance currently lists hybrid/connector setup from about €690; a WerkZ Box has hardware at the current purchase price plus provisioning from about €990; a fully customer-owned on-premises setup starts from about €2,490 additional project effort. These become binding only after the infrastructure assessment and an individual offer.
Clear maturity statements
What exists today, what needs project work, and what is a goal.
Existing foundations include the mobile WerkZ Time reference and technical Google Calendar and Microsoft 365 calendar adapters. Hybrid, on-premises and individual adapters require project-specific assessment and acceptance. DATEV, WhatsApp Business, Lexware Office, sevdesk, SFTP, WebDAV/Nextcloud and production electronic invoicing are goals or scoped options, not blanket claims of live standard connectors. No universal uptime, ISO certification, Germany-only hosting, grant or savings promise is made without specific evidence.
Must existing software be replaced?
No. An existing system can remain authoritative where it works and offers a suitable connection. Replacement is evaluated only if the desired workflow is blocked.
Which integrations are ready?
Google Calendar and Microsoft Graph/Microsoft 365 calendar have technical provider foundations. Every real customer connection needs its own configuration and acceptance. DATEV, Lexware Office, sevdesk, WhatsApp Business and other providers are not sold as universally finished live connectors.
Can WerkZ create XRechnung or ZUGFeRD?
Structured invoice data can be added to the architecture. A production e-invoice function is promised only after implementation and validation for the agreed scope.
Is WerkZ automatically GDPR compliant, ISO 27001 certified or hosted only in Germany?
No blanket certification or location claim is made. The actual data flow, subprocessors, contracts, access control, retention and deletion, backups, restore and provider/support chain must be assessed for the chosen deployment.
Can we start with a pilot?
Yes, with one or two defined workflows, systems, a test period, responsible people and measurable acceptance criteria. Its duration is planned after the pre-check and detail check, not promised as a universal number of weeks.
What happens if a connector fails?
The integration foundation uses observable job states, retry/backoff, dead-letter handling and idempotency. This is not a universal “exactly once” guarantee across all third-party systems.
Can we leave WerkZ later?
Export, handover, retention and deletion belong in the project and contract scope. Only implemented formats and handovers for the specific solution are promised.
Does it work on a smartphone?
The browser/PWA approach is central. The WerkZ Time reference was physically tested on iPhone/Safari. A native App Store app is not required for the basic approach. Each customer workflow still needs acceptance on its intended devices.
Which hosting model is safest?
Cloud, dedicated, hybrid, WerkZ Box and on-premises each have different operating and support needs. Existing suitable hardware is checked first. On-premises is not automatically safer.
Are grants guaranteed?
No. Official current programme terms must be checked for the individual project before it starts; funding is never guaranteed.
German-only detail pages currently contain the complete FAQ, legal notices, privacy statement, standard package pages and pre-check forms. Their links are marked “DE” where offered from English content.