Process carmation
Repetitive processes in sales, marketing or operations: carmated by n8n, Make or Python. You cut out data rewriting between five tools, generate offers, reports and data without a team clicking at night.
If you recognize at least two, it makes sense to talk about carmation.
01
Lead from the form entered manually into Customer Relationship Management. Offer generated in Word, sent by e-mail, entered back into Customer Relationship Management as a value. Returning customer: you are searching by name in three systems. It's not the tool's problem, it's the lack of an carmatic layer.
02
Newsletter, contact after the fair, payment reminder, segmentation by lead source. Each "send" involves clicking on three systems. No carmatic machine = the Same message arrives late or does not arrive at all.
03
Invoices with PDF e-mail entered into accounting, orders from Allegro transferred to the warehouse, monthly reports merged from three Excel exports. Any repetition means hours a week and room for human error.
04
SaaS pricing is calculated per task or operation. With a volume counted in tens or hundreds of thousands of operations per month, SaaS becomes more expensive than your own n8n server (VPS from PLN 50/month). You scale at no charge on a per-job basis.
A clickable prototype in a test environment before we write a single line of production code. Payment in four installments.
Week 1
A process map showing the current state of affairs (who does what, in which systems, and how long it yeses). A list of integrations (Customer Relationship Management, ERP, email, Allegro, online store). A decision on what to carmate in the MVP and what to address later. Deposit: 30%.
Weeks 2–3
Diagram of each process: trigger, steps, error paths, retry handling, alerts. Choice of system: n8n on your own server, Make / Zapier, or Python. Architectural decisions written in 2 pages, not 50.
End of Week 3
You approve the prototype. We won't start building the MVPithout your approval. Upon approval: another 30%.
Weeks 4–7
Implementation of processes with technical documentation. Each step tested in a test environment with your real data (anonymized). A demonstration of a working process every week. After the MVP release: another 30%.
Week 8
Migration of processes from the test environment to production. Monitoring configuration (Healthchecks, Slack/email alerts when the process goes down). Process documentation and handover to the client team: you can modify the process yourself. After implementation: last 10%.
The salesperson returns to sales instead of administration. Backoffice stops merging reports from three exports. It's not about "productivity" in the abstract, the point is that with the Same staff you will handle a larger volume of leads or orders.
The lead from the form will not disappear. The price from the offer is sent to Customer Relationship Management in the Same way as it was accepted. The PDF invoice is entered into accounting without a typo in the Tax Identification Number. Every person makes misyeses. Process no.
The process serves a volume limited only by the power of the server, not the number of hands. You increase your marketing funnel and your operational cost increases minimally. The employment of another admin assistant is 6-8 thousand. PLN/month, an additional process usually costs a fraction of that.
Every event recorded: when, who, what query, what response. GDPR compliant, easy diagnostics, easy management report. "Why didn't the client get an offer?": answer in 30 seconds, not after 3 days of questions from the team.
Apollo cold, Brevo welcome sequence, WordPress implementation, price collection: all our process. We don't sell what we don't use.
KG Electronics · Boiler Manufacturer
12 000
The controller sends data every 30 seconds, the backend aggregates, service alerts go to the administration panel. Classic IoT process = carmation layer over hardware. 12,000 connected devices, operational for 18 months.
View the full case studyDigital quoting · related service
3 hours → 4 minutes
In Akpil's case, the offer required 3 hours of the salesperson + approval from the boss. After carmation: 4 minutes from clicking in the PDF configurator in the customer's inbox. It's not just the interface: it's the process of generation, price mapping and shipping.
View digital biddingERP/Customer Relationship Management Integrations · Related Service
5 → 1
Most of our processes are based on the integration of 2-5 systems (Customer Relationship Management + ERP + mail + accounting + e-commerce). If the main problem is data synchronization between them, start with ERP/Customer Relationship Management integration, carmation will go a layer higher.
See integrationsTwo paths, two different company profiles.
Make / Zapier (SaaS without code)
n8n on your own server/Python
Make/Zapier are enough for simple processes. A dedicated solution is created when SaaS stops scaling, Polish APIs are non-standard, or data cannot leave the EU.
What happens after implementation, and who we are.
After implementation
Optional packages. We will discuss the details during a meeting after implementation.
See also
30 seconds on JSON Crew
A software company specializing in digital transformation for B2B sales. Product configurators, dashboards, and sales process carmation. Three key case studies (Akpil, Forest, and the internal JSON Hub platform) and portfolio implementations (KG Electronics, Metal Roofing, a heat recovery center, and modular homes).
Individual pricing based on the process map. Fixed price after specifying the scope, schedule 30 / 30 / 30 / 10. We price a single-stage machine (e.g. only contact via form) separately: faster and cheaper than the full process.
Make / Zapier are enough for simple, low-volume processes. We choose n8n on our own server (or Python) when: the volume is growing significantly, the integration is non-standard (Polish API, ERP), or the data is sensitive (GDPR) and cannot leave the EU. We give our recommendation after the first stage: we do not push dedicated solutions where SaaS is enough.
Three options: (1) Your infrastructure (AWS, your own server), (2) partner hosting (recommended: VPS under n8n, approx. PLN 50-200/month), (3) we host as part of the maintenance package. Decision after the first discovery stage: depends on GDPR requirements and infrastructure preferences.
Yes: n8n has a visual interface, documentation is provided in Polish. Your accountant or marketing specialist adds simple changes (e.g. adding a new step to contact the customer) without a programmer. Major architectural changes: either your developer or our on-demand support.
n8n on your server = data never leaves your infrastructure. Logs anonymized for up to 30 days (configurable). The data entrustment agreement is signed before the start. For regulated industries (medicine, finance), we recommend Python on your own server: full control.
Each process has monitoring (Healthchecks or its own alert to Slack/email). When integration goes wrong: alert within 5 minuteses, not after two days when the client calls. Minor maintenance fixes, major API changes (e.g. new version of Allegro): estimation separately.
Please describe the process you want to carmate and which systems it will connect. We will respond within one business day.
