[{"data":1,"prerenderedAt":2192},["ShallowReactive",2],{"home-offer-en":3,"navigation-en":1018,"language-switcher-\u002Fen":1067,"home-proof-en":1073,"home-journey-en":1324,"home-testimonials-en":1402,"home-insights-en":1403},[4,121,223,330,430,522,625,715,819,918],{"id":5,"title":6,"audience":7,"body":11,"description":40,"extension":41,"faq":42,"heroHeadline":55,"heroSubline":56,"keyword":57,"meta":58,"navGroup":59,"navLabel":60,"navigation":61,"order":62,"path":63,"pricingModels":64,"process":74,"relatedCase":91,"relatedPosts":92,"scope":94,"seo":107,"sitemap":108,"slug":118,"stem":119,"__hash__":120},"servicesEn\u002Fservices\u002Fweb-applications.md","Dedicated web applications",[8,9,10],"Companies whose core process still lives in spreadsheets and email","Teams paying for an off-the-shelf system they use 20% of","Organisations whose growth is blocked by tools that don't talk to each other",{"type":12,"value":13,"toc":33},"minimark",[14,19,23,26,30],[15,16,18],"h2",{"id":17},"when-a-dedicated-application-makes-sense","When a dedicated application makes sense",[20,21,22],"p",{},"An off-the-shelf system wins for as long as your process looks like everyone else's. Your competitive edge usually sits exactly where you do things differently — and that's precisely where boxed software starts getting in the way.",[20,24,25],{},"Signs it's time for your own system: the team keeps the \"real\" data in a spreadsheet next to the official tool, integration between systems means exporting to CSV, and every question about numbers costs an analyst a day.",[15,27,29],{"id":28},"what-we-wont-build","What we won't build",[20,31,32],{},"We don't build systems that can be assembled from off-the-shelf blocks. If the workshop shows that an existing tool plus two integrations is enough, we'll say so directly — it's cheaper for you and more honest toward both sides.",{"title":34,"searchDepth":35,"depth":35,"links":36},"",3,[37,39],{"id":17,"depth":38,"text":18},2,{"id":28,"depth":38,"text":29},"We build B2B systems, client portals and SaaS platforms shaped around your process, not a template. Quote within 3 business days.","md",[43,46,49,52],{"q":44,"a":45},"How much does a dedicated web application cost?","A simple internal system starts around PLN 60–90k net. A platform with multiple roles, integrations and a client portal is usually PLN 150–400k. We give an exact figure after the discovery workshop, because without understanding the process any number is a guess.",{"q":47,"a":48},"Who owns the code?","You do. We hand over the repository along with the proprietary rights in the contract. We don't license our own engine or use any other lock-in mechanism.",{"q":50,"a":51},"What happens if we end the engagement?","You get the repository, deployment documentation and infrastructure on your own accounts. The project is built to be handed to another team without needing our consent.",{"q":53,"a":54},"How long does building an MVP take?","From the workshop to the first production version, usually 3–5 months. Faster if the scope can be limited to a single process.","A web application built around your process","When spreadsheets stop being enough, and an off-the-shelf system forces you to change how you work, custom software is what's left.","dedicated web applications",{},"build","Web applications",true,1,"\u002Fservices\u002Fweb-applications",[65,68,71],{"name":66,"body":67},"Fixed price","For projects with a closed scope after the discovery workshop. You know the amount and the deadline before you start.",{"name":69,"body":70},"Time & material","For products that will evolve during the build. Billed for actual time, scope set iteratively.",{"name":72,"body":73},"Dedicated team","A standing team on your side, billed monthly. Makes sense for development that runs for quarters, not weeks.",[75,79,83,87],{"step":76,"duration":77,"body":78},"Discovery workshop","1–2 weeks","We map the process, define the MVP scope, and leave with a timeline and a quote.",{"step":80,"duration":81,"body":82},"Design and prototype","2–3 weeks","A clickable prototype of the key screens, so the idea gets validated before any code is written.",{"step":84,"duration":85,"body":86},"Build","8–16 weeks","Two-week iterations, each ending with a working version on a test environment.",{"step":88,"duration":89,"body":90},"Rollout and care","ongoing","Migration, training, monitoring and development on retainer.","dss-by-caredo",[93],"ile-kosztuje-aplikacja-webowa",[95,98,101,104],{"title":96,"body":97},"Process analysis and data model","Before the first screen exists, we document how the company actually works. This stage decides whether the system shortens the work or just adds another window to click through.",{"title":99,"body":100},"Interface built for daily use","Designed for people who'll spend eight hours a day in the system — keyboard shortcuts, bulk actions, sensible defaults.",{"title":102,"body":103},"Backend and API","Business logic, permissions, change auditing and an API ready to plug other systems into.",{"title":105,"body":106},"Rollout and data migration","We migrate data from spreadsheets and legacy systems, train the team, and stay close during the first weeks in production.",{"title":6,"description":40},{"loc":109,"alternatives":110},"\u002Fen\u002Fservices\u002Fweb-applications",[111,114,116],{"hreflang":112,"href":113},"x-default","\u002Fuslugi\u002Faplikacje-webowe",{"hreflang":115,"href":113},"pl-PL",{"hreflang":117,"href":109},"en-US","web-applications","services\u002Fweb-applications","6i-zLSV7ljanjtVOR8hvLNYf-VzNtIGQsk4ZtAhb7dw",{"id":122,"title":123,"audience":124,"body":128,"description":151,"extension":41,"faq":152,"heroHeadline":165,"heroSubline":166,"keyword":167,"meta":168,"navGroup":59,"navLabel":169,"navigation":61,"order":38,"path":170,"pricingModels":171,"process":177,"relatedCase":91,"relatedPosts":194,"scope":196,"seo":212,"sitemap":213,"slug":220,"stem":221,"__hash__":222},"servicesEn\u002Fservices\u002Ferp-systems.md","Dedicated ERP systems",[125,126,127],"Manufacturers and distributors whose process doesn't fit a standard module","Companies recovering from a failed off-the-shelf ERP rollout","Organisations with several systems that don't talk to each other",{"type":12,"value":129,"toc":147},[130,134,137,140,144],[15,131,133],{"id":132},"why-erp-rollouts-fail","Why ERP rollouts fail",[20,135,136],{},"The most common scenario doesn't look like a breakdown. It looks like this: the system works, the team uses it, and in parallel keeps a spreadsheet going because \"the system can't do that.\" A year later, the real data lives in the spreadsheet, and the ERP is an expensive historical record.",[20,138,139],{},"The cause almost always sits before the first line of code — in the assumption that the company will adapt to the tool. Sometimes that works. Usually it ends in a compromise nobody is happy with.",[15,141,143],{"id":142},"how-we-approach-it-differently","How we approach it differently",[20,145,146],{},"We start with an audit that documents the process as it is, workarounds included. Those workarounds aren't a pathology to eliminate — they're information about what the previous tool was missing.",{"title":34,"searchDepth":35,"depth":35,"links":148},[149,150],{"id":132,"depth":38,"text":133},{"id":142,"depth":38,"text":143},"We design and build ERP systems shaped around your company's process — orders, warehouse, production and finance in one place, without forcing the team to change how it works.",[153,156,159,162],{"q":154,"a":155},"Dedicated ERP or off-the-shelf?","Off-the-shelf wins when the process is standard and the budget is tight — the licence is cheaper than building. Dedicated wins when adapting an off-the-shelf system would cost more than writing your own, or when the process is a source of advantage you don't want flattened into someone else's model.",{"q":157,"a":158},"How long does a rollout take?","The first module usually reaches production after 3–4 months. Fully replacing an old system is typically one to two years, delivered module by module.",{"q":160,"a":161},"What about KSeF?","E-invoice handling is part of the sales module. If you already have an ERP and only need KSeF integration, that's a separate, much smaller service.",{"q":163,"a":164},"Will you take over a system from another vendor?","Yes, starting with a code and infrastructure audit. Sometimes the audit's outcome is a recommendation to rewrite rather than extend — we say so directly, with a cost justification.","An ERP system built for your company, not the other way round","Rolling out an off-the-shelf ERP is usually a project in organisational change. A dedicated system goes the other way — it describes how you already work, and removes the manual labour from it.","dedicated ERP system",{},"ERP systems","\u002Fservices\u002Ferp-systems",[172,175],{"name":173,"body":174},"By stage, each module quoted separately","Each module has its own scope, deadline and price. You can pause after any of them.",{"name":72,"body":176},"For multi-year rollouts — a standing team billed monthly.",[178,182,186,190],{"step":179,"duration":180,"body":181},"Process audit","2–4 weeks","We go department by department and document the document and data flow as it actually is.",{"step":183,"duration":184,"body":185},"Data model and scope","2 weeks","We decide what goes into the first rollout and what waits. Rolling out an ERP \"all at once\" is the most common cause of failure.",{"step":187,"duration":188,"body":189},"Build module by module","4–12 months","Module by module, each one reaching production before the next begins.",{"step":191,"duration":192,"body":193},"Migration and parallel running","1–3 months","A period where the old and new systems run side by side, until the team trusts the new one.",[195],"dedykowany-erp-czy-gotowy-system",[197,200,203,206,209],{"title":198,"body":199},"Orders and sales module","The flow from inquiry to invoice, with discount rules and credit limits under your control, not the software vendor's.",{"title":201,"body":202},"Warehouse and logistics","Real-time stock levels, reservations, picking, integration with scanners and couriers.",{"title":204,"body":205},"Production","Routings, work orders, material and labour accounting — modelled on your actual shop floor, not a textbook factory.",{"title":207,"body":208},"Reporting and dashboards","The numbers the board actually decides on, available without asking anyone for an export.",{"title":210,"body":211},"Integrations","Accounting, e-commerce, wholesalers, KSeF. An ERP without integrations just becomes another island.",{"title":123,"description":151},{"loc":214,"alternatives":215},"\u002Fen\u002Fservices\u002Ferp-systems",[216,218,219],{"hreflang":112,"href":217},"\u002Fuslugi\u002Fsystemy-erp",{"hreflang":115,"href":217},{"hreflang":117,"href":214},"erp-systems","services\u002Ferp-systems","UXJaKFUDBF0Z3ZTCb6FBD6QM9xXrlf11WO1nAkz9K5E",{"id":224,"title":225,"audience":226,"body":230,"description":253,"extension":41,"faq":254,"heroHeadline":267,"heroSubline":268,"keyword":269,"meta":270,"navGroup":271,"navLabel":272,"navigation":61,"order":35,"path":273,"pricingModels":274,"process":284,"relatedCase":91,"relatedPosts":301,"scope":303,"seo":319,"sitemap":320,"slug":327,"stem":328,"__hash__":329},"servicesEn\u002Fservices\u002Fintegrations-and-api.md","System integrations and APIs",[227,228,229],"Companies where the same information is entered by hand into two systems","Online stores whose stock levels drift out of sync","Taxpayers who must issue invoices through KSeF and have no mechanism for it",{"type":12,"value":231,"toc":249},[232,236,239,242,246],[15,233,235],{"id":234},"integration-isnt-a-one-off-project","Integration isn't a one-off project",[20,237,238],{},"Connecting two systems can be done in a week. Keeping it running for three years, through API changes on both sides, version migrations and seasonal volume spikes, is a completely different task — and that's what actually determines the real cost.",[20,240,241],{},"That's why we design every exchange assuming it will eventually break: retry queues, idempotent operations, an event log and alerts. An integration without that works great until the first exception.",[15,243,245],{"id":244},"ksef-without-panic","KSeF without panic",[20,247,248],{},"The e-invoice obligation turned integration from an option into a necessity. If you have your own sales system, you don't need to replace it — you need a layer that translates your invoices into the structured format, sends them, handles rejections, and archives the confirmations.",{"title":34,"searchDepth":35,"depth":35,"links":250},[251,252],{"id":234,"depth":38,"text":235},{"id":244,"depth":38,"text":245},"We connect ERP, CRM, e-commerce and wholesale systems into one data flow. We implement KSeF and build APIs you can rely on.",[255,258,261,264],{"q":256,"a":257},"How much does connecting two systems cost?","A simple connection through a well-documented API is usually PLN 8–20k net. Integrating with a system that has no API, requiring work on files or the database directly, can cost several times more — because the difficulty sits on that system's side, not ours.",{"q":259,"a":260},"What if my system has no API?","What's left is exchange files, database access, or interface automation. Each of those is worse than an API, and we say so directly, because it affects maintenance cost.",{"q":262,"a":263},"How long does a KSeF rollout take?","For a company with its own sales system, usually 3–6 weeks, including testing on the Ministry of Finance's pre-production environment.",{"q":265,"a":266},"What happens when an integration stops working?","Monitoring detects the gap in the exchange and sends an alert. Unprocessed documents wait in a queue and go through once the connection is restored — nothing disappears silently.","Your systems stop being islands","The most expensive integration is the one a person performs — copying data from one window to another, every day, with mistakes.","system integration",{},"improve","Integrations and APIs","\u002Fservices\u002Fintegrations-and-api",[275,278,281],{"name":276,"body":277},"Fixed price per integration","A single connection with a known scope — the most common model.",{"name":279,"body":280},"Integration bundle","Several systems at once, quoted together, with a lower rate per additional connection.",{"name":282,"body":283},"SLA retainer","Maintaining working integrations with a guaranteed response time for outages.",[285,289,293,297],{"step":286,"duration":287,"body":288},"System inventory","3–5 days","What needs to talk to what, in which direction, how often, and which system is the source of truth for each field.",{"step":290,"duration":291,"body":292},"Exchange design","1 week","Field mapping, conflict rules, error handling and volumes.",{"step":294,"duration":295,"body":296},"Rollout","2–8 weeks","Depending on the number of systems and whether they expose a reasonable API.",{"step":298,"duration":299,"body":300},"Observation","1 month","We run in production with heightened monitoring before handing off to maintenance.",[302],"ksef-integracja-systemu-firmowego",[304,307,310,313,316],{"title":305,"body":306},"ERP and accounting integrations","Documents, contacts and payments flow automatically, with error handling and a retry queue instead of records silently going missing.",{"title":308,"body":309},"E-commerce and marketplaces","Stock, prices, orders and shipping statuses synced both ways, with conflict resolution.",{"title":311,"body":312},"KSeF rollout","Issuing and receiving structured invoices, authentication, rejection handling and UPO archiving.",{"title":314,"body":315},"Custom APIs","We design and document APIs your partners and clients can plug into without your involvement.",{"title":317,"body":318},"Data exchange monitoring","An alert when synchronisation stops working — before you hear about it from a client.",{"title":225,"description":253},{"loc":321,"alternatives":322},"\u002Fen\u002Fservices\u002Fintegrations-and-api",[323,325,326],{"hreflang":112,"href":324},"\u002Fuslugi\u002Fintegracje-i-api",{"hreflang":115,"href":324},{"hreflang":117,"href":321},"integrations-and-api","services\u002Fintegrations-and-api","n1j28IOWWWSC0C0MOL_WuQ1u6Fwc7MmprwrJP06AKGM",{"id":331,"title":332,"audience":333,"body":337,"description":360,"extension":41,"faq":361,"heroHeadline":374,"heroSubline":375,"keyword":332,"meta":376,"navGroup":271,"navLabel":377,"navigation":61,"order":378,"path":379,"pricingModels":380,"process":390,"relatedCase":91,"relatedPosts":404,"scope":406,"seo":419,"sitemap":420,"slug":427,"stem":428,"__hash__":429},"servicesEn\u002Fservices\u002Fai-implementation.md","AI implementation for business",[334,335,336],"Teams drowning in documents to read, classify and retype","Support teams answering the same question for the thousandth time","Companies with a lot of internal knowledge nobody can find",{"type":12,"value":338,"toc":356},[339,343,346,349,353],[15,340,342],{"id":341},"why-ai-pilots-dont-reach-production","Why AI pilots don't reach production",[20,344,345],{},"A demo shows a model handling ten examples chosen by the person who prepared them. Production is ten thousand examples nobody chose, including scans crooked on the glass and documents in a format that wasn't in the test set.",[20,347,348],{},"The difference between the two isn't model quality. It's handling the cases where the model isn't sure — and that handling is the real substance of a rollout.",[15,350,352],{"id":351},"what-we-measure","What we measure",[20,354,355],{},"Before we start, we establish how long the work takes today and what share of cases the automation needs to handle for the rollout to make sense. After launch, the same metric tells us whether it's working. Without it, \"AI in the company\" is a cost with no verifiable return.",{"title":34,"searchDepth":35,"depth":35,"links":357},[358,359],{"id":341,"depth":38,"text":342},{"id":351,"depth":38,"text":352},"We deploy AI where it genuinely shortens real work — document classification, search over internal knowledge, support assistants. No pilots that never reach production.",[362,365,368,371],{"q":363,"a":364},"Where do we start with AI in our company?","With one process that's repetitive, has a measurable time cost, and tolerates the occasional mistake. Classifying incoming documents usually meets all three. Starting with \"an assistant that knows everything\" is the most common way to get a project with no end.",{"q":366,"a":367},"Will my data go to a public model?","Not unless you want it to. We match the solution to your requirements — from hosted models under a no-training-on-data agreement, to models run on your own infrastructure.",{"q":369,"a":370},"What if the model gets it wrong?","We design assuming it will. Every rollout has a confidence threshold — above it, the automation runs; below it, the case goes to a human. Every model decision is logged and traceable.",{"q":372,"a":373},"What does it cost?","A prototype is usually PLN 15–30k net. A production rollout is PLN 60–200k, depending on the number of integrations. On top of that, the cost of running the models — typically hundreds to a few thousand zloty a month.","AI deployed where it actually saves time","Most corporate AI projects end at the demo. We start by asking which repetitive work you want gone — and whether its disappearance can be measured.",{},"AI implementation",4,"\u002Fservices\u002Fai-implementation",[381,384,387],{"name":382,"body":383},"Fixed-price prototype","Quoted separately and deliberately small. If accuracy comes in below the threshold, we stop — and that's a good outcome too, just a cheaper one than finding out a year in.",{"name":385,"body":386},"Fixed-price rollout","Once the prototype exists the scope is known, so we can give an amount and a deadline.",{"name":388,"body":389},"Maintenance retainer","Accuracy monitoring, tuning and model updates.",[391,394,397,401],{"step":392,"duration":291,"body":393},"Choosing the use case","We review the candidates and pick the one with the best ratio of time saved to risk. We define the success metric before starting.",{"step":395,"duration":81,"body":396},"Prototype on your data","A working prototype on real documents, with measured accuracy. This is the decision point on whether to continue.",{"step":398,"duration":399,"body":400},"Production rollout","4–10 weeks","Integration with your systems, handling of uncertain cases, permissions and a model decision log.",{"step":402,"duration":89,"body":403},"Measurement and tuning","Accuracy measured continuously, because data changes — a model that worked in March may not work in November.",[405],"wdrozenie-ai-w-firmie-od-czego-zaczac",[407,410,413,416],{"title":408,"body":409},"Document classification and extraction","Invoices, contracts, orders and correspondence read automatically, with fields extracted into your system and a queue of uncertain cases for a human to decide.",{"title":411,"body":412},"Search over company knowledge","A question asked in plain language, an answer with a link to the source document. No making things up — if the answer isn't in the knowledge base, the system says so.",{"title":414,"body":415},"Customer support assistants","Answers to repetitive questions, handed off to a human the moment confidence drops.",{"title":417,"body":418},"Automation with a model in the loop","The model as one step in a process, not the whole process — with the output validated before it's written to the system.",{"title":332,"description":360},{"loc":421,"alternatives":422},"\u002Fen\u002Fservices\u002Fai-implementation",[423,425,426],{"hreflang":112,"href":424},"\u002Fuslugi\u002Fwdrozenia-ai",{"hreflang":115,"href":424},{"hreflang":117,"href":421},"ai-implementation","services\u002Fai-implementation","JRpvH1T996kqI1_eb4j8O7Zhl72twBMjnOeKMf2EEUU",{"id":431,"title":432,"audience":433,"body":437,"description":452,"extension":41,"faq":453,"heroHeadline":466,"heroSubline":467,"keyword":468,"meta":469,"navGroup":271,"navLabel":470,"navigation":61,"order":471,"path":472,"pricingModels":473,"process":480,"relatedCase":493,"relatedPosts":494,"scope":495,"seo":511,"sitemap":512,"slug":519,"stem":520,"__hash__":521},"servicesEn\u002Fservices\u002Fprocess-automation.md","Business process automation",[434,435,436],"Teams spending days on reports that get built the same way every month","Companies where approving a document means an email chain","Organisations hiring more people to do work a rule could do",{"type":12,"value":438,"toc":449},[439,443,446],[15,440,442],{"id":441},"automation-starts-with-a-spreadsheet-of-hours","Automation starts with a spreadsheet of hours",[20,444,445],{},"Before we write anything, we want to know how many times a month the process runs and how long it takes each time. That number tells us how much is reasonable to spend on automating it — and whether it's worth it at all.",[20,447,448],{},"Surprisingly often, the process that annoys everyone costs four hours a month — and the one nobody talks about, because \"it's always been done that way,\" eats two full-time roles.",{"title":34,"searchDepth":35,"depth":35,"links":450},[451],{"id":441,"depth":38,"text":442},"We remove repetitive manual work — document flows, reports, retyping data between systems. We start with the process that costs the most hours.",[454,457,460,463],{"q":455,"a":456},"Which process should we start with?","The one performed most often with the fewest exceptions — not the most annoying one. Annoyance and cost are two different things, and automating a process full of exceptions can end up more expensive than doing it by hand.",{"q":458,"a":459},"Does automation mean layoffs?","In practice, usually not. What disappears is work nobody wanted to do, and the team takes on things there was never time for before. If the goal is headcount reduction, we'll say honestly whether a given process can carry that.",{"q":461,"a":462},"How long until it pays for itself?","With a well-chosen process, usually 6–12 months. That's why we start by counting hours — without that, it's guesswork.",{"q":464,"a":465},"How is this different from off-the-shelf no-code tools?","It isn't, if your process fits what they can do — then we'll point you to a tool instead of writing code. The difference shows up with rules those tools can't express, and at volumes where they start getting expensive.","Work no one should be doing by hand","Every company has a few processes that eat up a full-time role and amount to moving information from one place to another.","business process automation",{},"Process automation",5,"\u002Fservices\u002Fprocess-automation",[474,477],{"name":475,"body":476},"Fixed price per process","One process, known scope, known price. The most common and safest model.",{"name":478,"body":479},"Automation retainer","A fixed monthly pool of hours for further automations, for companies that want to go process by process.",[481,484,487,490],{"step":482,"duration":291,"body":483},"Audit and process selection","We review the candidates and pick the one with the best savings-to-difficulty ratio.",{"step":485,"duration":77,"body":486},"Rule design","We write down the edge cases and exceptions. They decide success, not the happy path.",{"step":294,"duration":488,"body":489},"2–6 weeks","The automation runs alongside the manual process, so results can be compared.",{"step":491,"duration":180,"body":492},"Switchover and expansion","We turn off the manual version and move on to the next process.","2motion",[405],[496,499,502,505,508],{"title":497,"body":498},"Process map and hour count","We start by counting how much time the process costs today. Without that number, there's no way to judge whether automating it pays off.",{"title":500,"body":501},"Document and approval flows","Requests, orders and invoices with approval rules, reminders and a decision history.",{"title":503,"body":504},"Automatically generated reports","The summaries a person compiles today, built by themselves and delivered wherever they need to land.",{"title":506,"body":507},"Data synchronisation","No more retyping the same record into three systems.",{"title":509,"body":510},"Notifications and escalations","The system watches deadlines instead of a person who has to remember them.",{"title":432,"description":452},{"loc":513,"alternatives":514},"\u002Fen\u002Fservices\u002Fprocess-automation",[515,517,518],{"hreflang":112,"href":516},"\u002Fuslugi\u002Fautomatyzacja-procesow",{"hreflang":115,"href":516},{"hreflang":117,"href":513},"process-automation","services\u002Fprocess-automation","dWXLPn_QIMw3rILavszqeESlo1LijXwS70wlg6LmA0M",{"id":523,"title":524,"audience":525,"body":529,"description":552,"extension":41,"faq":553,"heroHeadline":566,"heroSubline":567,"keyword":568,"meta":569,"navGroup":59,"navLabel":570,"navigation":61,"order":571,"path":572,"pricingModels":573,"process":583,"relatedCase":493,"relatedPosts":597,"scope":598,"seo":614,"sitemap":615,"slug":622,"stem":623,"__hash__":624},"servicesEn\u002Fservices\u002Fwebsites.md","Website design and development",[526,527,528],"Companies whose website generates no inquiries at all","Organisations running a slow, hard-to-edit site on an outdated platform","Teams preparing a campaign that needs a landing page built for conversion",{"type":12,"value":530,"toc":548},[531,535,538,541,545],[15,532,534],{"id":533},"speed-isnt-a-technical-detail","Speed isn't a technical detail",[20,536,537],{},"Google measures mobile load time and factors it into ranking, and a visitor closes the tab before the content even appears. A site that takes four seconds to load loses half its visitors before they see anything.",[20,539,540],{},"That's why we build statically: the HTML is ready before anyone arrives, and JavaScript only shows up where it's actually needed.",[15,542,544],{"id":543},"remote-delivery-anywhere","Remote delivery, anywhere",[20,546,547],{},"We're happy to meet in person, but most projects run remotely, for clients across Poland and abroad — location doesn't affect price or pace.",{"title":34,"searchDepth":35,"depth":35,"links":549},[550,551],{"id":533,"depth":38,"text":534},{"id":543,"depth":38,"text":544},"We design fast, accessible company websites and landing pages optimised for search. Serving Poland and international clients, remote delivery.",[554,557,560,563],{"q":555,"a":556},"How much does a company website cost?","A landing page from PLN 8k net. A company site with a dozen or so pages and a blog is usually PLN 25–60k. The biggest share of the budget is usually content and photography, not code — worth planning for upfront.",{"q":558,"a":559},"Will I be able to edit the content myself?","Yes. By default we ship content as files versioned in the repository, which is the fastest and safest option. If you need a panel for a non-technical person, we set up a headless CMS — a decision made during the workshop, since it affects cost and maintenance.",{"q":561,"a":562},"What about SEO after launch?","The site leaves us with correct technical SEO and a phrase-based content architecture. That's necessary, not sufficient — rankings are built by content and links over time.",{"q":564,"a":565},"Do you migrate an existing site?","Yes, along with a redirect map from the old URLs. Skipping that step is the most common cause of losing traffic after a rebuild.","A site that loads instantly and brings in inquiries","Most company websites look good in a screenshot and lose in search. We build the other way round: performance and content first, effects second.","website design and development",{},"Websites",6,"\u002Fservices\u002Fwebsites",[574,577,580],{"name":575,"body":576},"Landing page","One page for a campaign, from PLN 8k net.",{"name":578,"body":579},"Company website","A dozen or so pages, a blog, forms — usually PLN 25–60k net.",{"name":581,"body":582},"Multilingual site","The above, plus a second language version with correct hreflang.",[584,587,590,594],{"step":585,"duration":291,"body":586},"Workshop and architecture","Goals, audiences, the subpage map and target phrases.",{"step":588,"duration":81,"body":589},"Design","Design of the key templates; everything else is built from them.",{"step":591,"duration":592,"body":593},"Build and content","3–5 weeks","Coding, content entry, testing across devices.",{"step":595,"duration":291,"body":596},"Launch and measurement","Redirects from old URLs, Search Console, analytics.",[93],[599,602,605,608,611],{"title":600,"body":601},"Content architecture around search phrases","We decide which page answers which query, so subpages don't compete against each other in results.",{"title":603,"body":604},"Design and build","A layout shaped by the content, not the other way round. Responsive from 320 pixels up.",{"title":606,"body":607},"Performance","Static generation, modern image formats, no unnecessary JavaScript. The goal is green Core Web Vitals on mobile.",{"title":609,"body":610},"Technical SEO","Structured data, sitemap, canonical URLs, correct headings and meta tags.",{"title":612,"body":613},"Accessibility","Contrast, keyboard navigation, sensible semantics. A legal requirement for public bodies and plain decency for everyone else.",{"title":524,"description":552},{"loc":616,"alternatives":617},"\u002Fen\u002Fservices\u002Fwebsites",[618,620,621],{"hreflang":112,"href":619},"\u002Fuslugi\u002Fstrony-internetowe",{"hreflang":115,"href":619},{"hreflang":117,"href":616},"websites","services\u002Fwebsites","dSX-BlQ2jnf4dhQoUmDq_k-FNDZMnndIkJEfOAep1uw",{"id":626,"title":627,"audience":628,"body":632,"description":647,"extension":41,"faq":648,"heroHeadline":661,"heroSubline":662,"keyword":663,"meta":664,"navGroup":59,"navLabel":665,"navigation":61,"order":666,"path":667,"pricingModels":668,"process":674,"relatedCase":493,"relatedPosts":687,"scope":688,"seo":704,"sitemap":705,"slug":712,"stem":713,"__hash__":714},"servicesEn\u002Fservices\u002Fmobile-applications.md","Mobile applications for business",[629,630,631],"Companies that need an app for field staff","Products with an existing backend that need a mobile channel","Teams whose separate iOS and Android versions have drifted apart feature-wise",{"type":12,"value":633,"toc":644},[634,638,641],[15,635,637],{"id":636},"offline-is-harder-than-it-looks","Offline is harder than it looks",[20,639,640],{},"An app for a warehouse worker or field technician runs in places where signal disappears. That means a local database, an operation queue, and rules for resolving conflicts when the same record changed in two places.",[20,642,643],{},"This part of the project is sometimes bigger than the entire interface, and it's easy to leave out of a quote. We ask about it in the first meeting.",{"title":34,"searchDepth":35,"depth":35,"links":645},[646],{"id":636,"depth":38,"text":637},"We build mobile apps in React Native and Flutter — one codebase, iOS and Android, faster time to launch and cheaper maintenance.",[649,652,655,658],{"q":650,"a":651},"React Native or Flutter?","If you have a web team working in React, React Native lets them co-build the app and share some logic. Flutter gives a more predictable look across both platforms and handles heavy animation better. We give a recommendation once we know your team, because maintenance lasts longer than the build.",{"q":653,"a":654},"Do I need separate native versions?","Rarely. They're justified by performance requirements, deep hardware access, or system integrations a cross-platform layer doesn't cover. We'll tell you if your case is one of them.",{"q":656,"a":657},"How much does a mobile app cost?","An app for field staff with offline work is usually PLN 90–250k net. A simple client for an existing API can be cheaper. On top of that: annual Apple and Google developer account fees.",{"q":659,"a":660},"Who publishes the app in the stores?","We publish under your own accounts, so ownership of the app and its analytics stay on your side. We set them up together with you at the start of the project.","One codebase, both platforms","Separate native apps make sense for games and heavy graphics. For a business application, they double the cost and slow down every release.","mobile applications for business",{},"Mobile applications",7,"\u002Fservices\u002Fmobile-applications",[669,672],{"name":670,"body":671},"Fixed price after prototype","Scope is known once the mockup exists, so we can give an amount and a deadline.",{"name":69,"body":673},"For products whose shape will keep changing with market feedback.",[675,678,681,684],{"step":676,"duration":291,"body":677},"Scope and technology choice","What it needs to do, what it runs on, what has to work offline.",{"step":679,"duration":184,"body":680},"Interface prototype","A clickable mockup on-device, tested by the people who'll actually use it.",{"step":84,"duration":682,"body":683},"10–20 weeks","Iterations, with versions available through a test channel.",{"step":685,"duration":89,"body":686},"Launch and growth","Release, crash monitoring, further versions.",[93],[689,692,695,698,701],{"title":690,"body":691},"React Native or Flutter application","The technology choice depends on the project, not our preferences — it's decided by the existing stack, library availability, and who will maintain the code.",{"title":693,"body":694},"Offline-first work","A field app has to work with no signal and sync once it's back online. This is the part of the project most often underestimated.",{"title":696,"body":697},"Device integration","Camera, barcode scanner, GPS, push notifications, biometrics.",{"title":699,"body":700},"App store publishing","We run the process in the App Store and Google Play, including rejections and appeals.",{"title":702,"body":703},"Releases and telemetry","Test channels, crash reporting and usage statistics from the first version onward.",{"title":627,"description":647},{"loc":706,"alternatives":707},"\u002Fen\u002Fservices\u002Fmobile-applications",[708,710,711],{"hreflang":112,"href":709},"\u002Fuslugi\u002Faplikacje-mobilne",{"hreflang":115,"href":709},{"hreflang":117,"href":706},"mobile-applications","services\u002Fmobile-applications","vmVbp-gW_e1l-VhWd2VwdXl6lGqV0yPsMi2eyYKqf7M",{"id":716,"title":717,"audience":718,"body":722,"description":745,"extension":41,"faq":746,"heroHeadline":759,"heroSubline":760,"keyword":761,"meta":762,"navGroup":271,"navLabel":763,"navigation":61,"order":764,"path":765,"pricingModels":766,"process":776,"relatedCase":91,"relatedPosts":791,"scope":792,"seo":808,"sitemap":809,"slug":816,"stem":817,"__hash__":818},"servicesEn\u002Fservices\u002Fcode-audit-and-project-takeover.md","Code audit and project takeover",[719,720,721],"Companies that parted ways with their team, left with code nobody understands","Boards facing an investment decision, needing an independent technical assessment","Product owners where every release breaks something else",{"type":12,"value":723,"toc":741},[724,728,731,734,738],[15,725,727],{"id":726},"the-most-common-findings","The most common findings",[20,729,730],{},"No backups, or backups nobody has ever restored. Production keys committed to the repository. Dependencies untouched for years, with publicly known vulnerabilities. Deployment done by hand by one person, who has since left.",[20,732,733],{},"None of it is a death sentence. All of it is fixable — provided someone names it first.",[15,735,737],{"id":736},"when-we-recommend-a-rewrite","When we recommend a rewrite",[20,739,740],{},"Rarely, and only when the cost of getting the existing code to a state where it can be changed safely exceeds the cost of writing it from scratch. In practice that usually means: no tests whatsoever, unsupported technology, and an architecture that makes any change impossible without rewriting half the system.",{"title":34,"searchDepth":35,"depth":35,"links":742},[743,744],{"id":726,"depth":38,"text":727},{"id":736,"depth":38,"text":737},"We take over development from another vendor. We start with a code and infrastructure audit that says plainly what can be saved and what needs to be rewritten.",[747,750,753,756],{"q":748,"a":749},"What if the previous vendor won't hand over access?","It happens more often than it should. We help reconstruct the infrastructure from what's available and flag what's missing. It's worth checking in advance whose accounts the domain, hosting and repository sit on — that's the most common flashpoint.",{"q":751,"a":752},"Is the audit unbiased if you want to take the project over yourselves?","A fair question. That's why the audit can be bought separately and used with any vendor. A recommendation to rewrite is financially better for us, so when we recommend extending the existing code — which is what we do most often — that goes against our own short-term interest.",{"q":754,"a":755},"How long does it take to get up to speed on someone else's code?","For a mid-sized project with any documentation at all, 2–3 weeks to the first safe changes. With no tests and no documentation, it can take twice as long.",{"q":757,"a":758},"What do I get in the report?","A risk list ranked by the cost of ignoring each one, a code and infrastructure quality assessment, a list of security vulnerabilities, and a recommendation with costs for both options. Written so the board can understand it, with a technical appendix for developers.","The project stalled. We'll take it over and tell you the truth about its condition","When the relationship with the previous vendor ends, the first question isn't \"how much to fix this\" — it's \"what is even here.\"","taking over a project from a software house",{},"Code audit and takeover",8,"\u002Fservices\u002Fcode-audit-and-project-takeover",[767,770,773],{"name":768,"body":769},"Audit only, fixed price","From PLN 12k net. Ends with a report that's yours to keep and doesn't commit you to further work with us.",{"name":771,"body":772},"Audit with takeover","The audit cost is credited against the first month of development.",{"name":774,"body":775},"Development after takeover","Time & material or an SLA retainer, depending on the pace of change.",[777,781,784,788],{"step":778,"duration":779,"body":780},"Access and first review","2–3 days","Repository, infrastructure, documentation. This stage alone often surfaces the most serious risks.",{"step":782,"duration":77,"body":783},"The audit itself","Code and infrastructure analysis, ending in a report with a risk list and a recommendation.",{"step":785,"duration":786,"body":787},"Report walkthrough","1 meeting","We go through the findings and agree a plan together. You can stop here and use the report elsewhere.",{"step":789,"duration":488,"body":790},"Takeover","Stabilisation, cleaning up deployments, and settling into a normal development rhythm.",[195],[793,796,799,802,805],{"title":794,"body":795},"Code audit","Quality, technical debt, test coverage, dependency freshness and security vulnerabilities. With a risk list ranked by the cost of leaving each one unaddressed.",{"title":797,"body":798},"Infrastructure audit","Where it runs, who has access, what deployment looks like, whether backups exist, and whether anyone has ever confirmed they can be restored.",{"title":800,"body":801},"Takeover feasibility assessment","How long it'll take a new team to get up to speed, and what needs doing first to ship changes safely.",{"title":803,"body":804},"Recommendation: extend or rewrite","With a cost comparison of both options. Rewriting is sometimes cheaper, but far less often than first impressions suggest.",{"title":806,"body":807},"Takeover and stabilisation","Cleaning up deployments, adding tests in the riskiest spots, and taking over ongoing development.",{"title":717,"description":745},{"loc":810,"alternatives":811},"\u002Fen\u002Fservices\u002Fcode-audit-and-project-takeover",[812,814,815],{"hreflang":112,"href":813},"\u002Fuslugi\u002Faudyt-i-przejecie-projektu",{"hreflang":115,"href":813},{"hreflang":117,"href":810},"code-audit-and-project-takeover","services\u002Fcode-audit-and-project-takeover","EWZzpaLCzH7LvPyTizItdvW_unSDmE9ObjaWmOKwDvo",{"id":820,"title":821,"audience":822,"body":826,"description":849,"extension":41,"faq":850,"heroHeadline":863,"heroSubline":864,"keyword":865,"meta":866,"navGroup":271,"navLabel":867,"navigation":61,"order":868,"path":869,"pricingModels":870,"process":880,"relatedCase":91,"relatedPosts":890,"scope":891,"seo":907,"sitemap":908,"slug":915,"stem":916,"__hash__":917},"servicesEn\u002Fservices\u002Fmaintenance-and-support.md","Application maintenance and development",[823,824,825],"Companies where one person maintains the system and everyone dreads their holiday","Organisations with no monitoring, finding out about outages from clients","Teams whose development has stalled because there's no one to ship changes",{"type":12,"value":827,"toc":845},[828,832,835,838,842],[15,829,831],{"id":830},"the-most-common-outage-scenario","The most common outage scenario",[20,833,834],{},"It isn't a spectacular breach or an attack. It's an expired certificate, a full disk, or a dependency update that changed behaviour somewhere nobody tested.",[20,836,837],{},"All three are cheap to catch in advance and expensive to learn about from a client on a Friday afternoon.",[15,839,841],{"id":840},"why-we-test-backups","Why we test backups",[20,843,844],{},"A backup nobody has ever restored is a hypothesis, not a safeguard. Once a quarter, we restore it on a test environment and check that the system actually comes up and the data checks out.",{"title":34,"searchDepth":35,"depth":35,"links":846},[847,848],{"id":830,"depth":38,"text":831},{"id":840,"depth":38,"text":841},"Post-launch care with a committed response time — monitoring, security updates and ongoing development on a retainer.",[851,854,857,860],{"q":852,"a":853},"Do you maintain systems you didn't build?","Yes, after an audit. The audit is needed to know what we're taking over and what response time we can honestly promise. Sometimes its outcome is a list of things to fix before care begins.",{"q":855,"a":856},"What does response time mean?","The time from a report to starting work on the problem, not to resolving it. A production outage is usually 4 business hours under the basic plan. Fix time depends on the cause, and no honest provider guarantees it upfront.",{"q":858,"a":859},"What if I don't use all my hours in a given month?","Unused hours roll over to the next month, up to one month's pool. They don't accumulate indefinitely — that turns a retainer into a bank of hours and breaks planning on both sides.",{"q":861,"a":862},"Can I cancel?","With one month's notice. On leaving, we hand over operational documentation and access — the project is built to be transferable.","A system needs someone watching it after launch","Software doesn't break on its own, but the world around it keeps changing — libraries, browsers, regulations and traffic scale.","web application maintenance",{},"Maintenance and support",9,"\u002Fservices\u002Fmaintenance-and-support",[871,874,877],{"name":872,"body":873},"Basic care","Monitoring, security updates and incident response. From PLN 2.5k net a month.",{"name":875,"body":876},"Care with development","The above plus a fixed pool of hours for changes. From PLN 8k net a month.",{"name":878,"body":879},"Extended SLA","Shorter response time, after-hours on-call. Quoted individually.",[881,884,887],{"step":882,"duration":77,"body":883},"System handover","We get to know the code and infrastructure, set up monitoring and check the backups.",{"step":885,"duration":786,"body":886},"Setting the SLA","Response time, maintenance window, escalation path and the list of decision-makers.",{"step":888,"duration":89,"body":889},"Ongoing care","Monitoring, updates, development and a report at month's end.",[93],[892,895,898,901,904],{"title":893,"body":894},"Monitoring and incident response","Uptime, errors and performance watched around the clock, with an alert to us before your client notices.",{"title":896,"body":897},"Security updates","Dependencies updated regularly, critical vulnerabilities patched out of turn.",{"title":899,"body":900},"Backups and recovery","Backups taken automatically and periodically proven by an actual restore. An untested backup isn't a backup.",{"title":902,"body":903},"Development on retainer","A monthly pool of hours for changes and new features, without negotiating a separate contract every time.",{"title":905,"body":906},"Monthly report","What happened, what we updated, where the hours went, and what we recommend next.",{"title":821,"description":849},{"loc":909,"alternatives":910},"\u002Fen\u002Fservices\u002Fmaintenance-and-support",[911,913,914],{"hreflang":112,"href":912},"\u002Fuslugi\u002Futrzymanie-i-rozwoj",{"hreflang":115,"href":912},{"hreflang":117,"href":909},"maintenance-and-support","services\u002Fmaintenance-and-support","6eSWl4HFZWH41RSD83jHivvdkr3rsQ9G62IZkYrcjEo",{"id":919,"title":920,"audience":921,"body":925,"description":948,"extension":41,"faq":949,"heroHeadline":962,"heroSubline":963,"keyword":964,"meta":965,"navGroup":966,"navLabel":76,"navigation":61,"order":967,"path":968,"pricingModels":969,"process":976,"relatedCase":493,"relatedPosts":990,"scope":991,"seo":1007,"sitemap":1008,"slug":1015,"stem":1016,"__hash__":1017},"servicesEn\u002Fservices\u002Fdiscovery-workshop.md","Discovery workshop and MVP estimate",[922,923,924],"Companies facing an investment decision, needing a real scope and budget","Startups ahead of their first funding round, where an investor wants an execution plan","Teams that got three quotes an order of magnitude apart and don't know why",{"type":12,"value":926,"toc":944},[927,931,934,937,941],[15,928,930],{"id":929},"why-three-quotes-differ-by-an-order-of-magnitude","Why three quotes differ by an order of magnitude",[20,932,933],{},"Because they answer three different questions. One vendor quoted exactly what they were told. Another added everything they thought would be needed. A third quoted low, banking on change orders later.",[20,935,936],{},"None of these quotes is comparable to the others until a shared description of the scope exists. The workshop creates that description — and only then does comparing quotes make sense.",[15,938,940],{"id":939},"what-you-get-at-the-end","What you get at the end",[20,942,943],{},"A document of a dozen or so pages: a process map, the scope of the first rollout, a list of things deliberately deferred, an architecture sketch, risks, a timeline and a quote with its assumptions. Plus a clickable prototype of the most important screen.",{"title":34,"searchDepth":35,"depth":35,"links":945},[946,947],{"id":929,"depth":38,"text":930},{"id":939,"depth":38,"text":940},"A paid workshop that leaves you with a scope, timeline and quote — whether or not we end up building it together.",[950,953,956,959],{"q":951,"a":952},"Why is the workshop paid?","Because it's work, not a sales pitch. The output is yours, and you can take it to any vendor — including one that isn't us. A free quote is free because it's a guess, and its cost is baked into the project anyway.",{"q":954,"a":955},"What if I decide not to build after the workshop?","That's a good outcome. Better to spend a modest amount finding out a project doesn't make sense than several hundred thousand finding out a year in. The document stays with you.",{"q":957,"a":958},"Who should take part?","A business decision-maker, someone who knows the process operationally, and — if there is one — a technical person. Three to five people. Beyond that, the workshop turns into a general meeting.",{"q":960,"a":961},"Is the quote binding?","The quote is binding for the scope described in the document, under the assumptions written into it. If the scope changes, the amount changes — but you'll know exactly which line item and by how much.","Before you decide to build, find out exactly what you're building","A free quote based on a one-hour call is a guess wrapped in a PDF. A discovery workshop gives you a number you can defend.","application cost estimate",{},"start",10,"\u002Fservices\u002Fdiscovery-workshop",[970,973],{"name":971,"body":972},"Fixed-price workshop","From PLN 9k net, depending on scale. You know the amount before you start.",{"name":974,"body":975},"Credited toward the build","If you decide to build with us, the workshop cost is deducted from the first project invoice.",[977,981,984,987],{"step":978,"duration":979,"body":980},"Preparation","3 days","We gather materials, confirm participants, and send questions to think about before the session.",{"step":982,"duration":77,"body":983},"Workshops","Sessions of 2–3 hours. Shorter than all-day marathons nobody remembers afterwards.",{"step":985,"duration":291,"body":986},"Write-up","We write the document, sketch the prototype, and work out the quote.",{"step":988,"duration":786,"body":989},"Handover","We walk through the document and answer questions. The material stays with you.",[93],[992,995,998,1001,1004],{"title":993,"body":994},"Workshop sessions","Two to four sessions with decision-makers and with the people who'll actually use the system. The latter usually know more.",{"title":996,"body":997},"Process map and scope","A description of the current and target state, with a clear line between the first rollout and later phases.",{"title":999,"body":1000},"Architecture sketch","How it should be built, what it integrates with, and which technical risks are already visible.",{"title":1002,"body":1003},"Timeline and quote","Stages with dates and amounts, along with the assumptions they rest on. Change an assumption and the number changes — and you know by how much.",{"title":1005,"body":1006},"Prototype of the key screen","A clickable mockup of the most important view, so the conversation has something concrete to focus on.",{"title":920,"description":948},{"loc":1009,"alternatives":1010},"\u002Fen\u002Fservices\u002Fdiscovery-workshop",[1011,1013,1014],{"hreflang":112,"href":1012},"\u002Fuslugi\u002Fwarsztat-discovery",{"hreflang":115,"href":1012},{"hreflang":117,"href":1009},"discovery-workshop","services\u002Fdiscovery-workshop","Uru7kYiWr0XPyN3uLNbAiknhzJotuqrRwO8HiprogSs",{"services":1019,"industries":1030,"caseStudies":1051},[1020,1021,1022,1023,1024,1025,1026,1027,1028,1029],{"slug":118,"navLabel":60,"navGroup":59,"heroHeadline":55},{"slug":220,"navLabel":169,"navGroup":59,"heroHeadline":165},{"slug":327,"navLabel":272,"navGroup":271,"heroHeadline":267},{"slug":427,"navLabel":377,"navGroup":271,"heroHeadline":374},{"slug":519,"navLabel":470,"navGroup":271,"heroHeadline":466},{"slug":622,"navLabel":570,"navGroup":59,"heroHeadline":566},{"slug":712,"navLabel":665,"navGroup":59,"heroHeadline":661},{"slug":816,"navLabel":763,"navGroup":271,"heroHeadline":759},{"slug":915,"navLabel":867,"navGroup":271,"heroHeadline":863},{"slug":1015,"navLabel":76,"navGroup":966,"heroHeadline":962},[1031,1035,1039,1043,1047],{"slug":1032,"navLabel":1033,"heroHeadline":1034},"manufacturing","Manufacturing","The works order reaches the floor as a printout from an email",{"slug":1036,"navLabel":1037,"heroHeadline":1038},"automotive","Automotive","The customer exists in three places at once",{"slug":1040,"navLabel":1041,"heroHeadline":1042},"industrial-automation","Industrial automation","You sell competence that doesn't photograph",{"slug":1044,"navLabel":1045,"heroHeadline":1046},"e-commerce","E-commerce","The shop works. What sits behind it comes apart",{"slug":1048,"navLabel":1049,"heroHeadline":1050},"logistics","Transport and logistics","The job arrives by email, the status comes back by phone",[1052,1058,1063],{"slug":91,"client":1053,"tag":1054,"year":1055,"summary":1056,"image":1057},"Caredo","Product",2025,"We build the whole DSS product together with the Caredo team — from the CRM and planner to the software behind the key lockers and totems.","\u002Fimg\u002Fcase-studies\u002Fdss\u002Fkluczykomat\u002Fframe_0169.webp",{"slug":1059,"client":1053,"tag":1060,"year":1055,"summary":1061,"image":1062},"dss-by-caredo-website","Product website","We built the DSS product website end to end — from design to launch — on Caredo's visual identity.","\u002Fimg\u002Fscreenshots\u002Fdss-desktop.jpg",{"slug":493,"client":493,"tag":1064,"year":1055,"summary":1065,"image":1066},"Brand and website","A whole brand from scratch — logo, colours, business cards — a company website and blog posts that position 2motion in search.","\u002Fimg\u002Fscreenshots\u002F2motion-desktop.jpg",[1068],{"code":1069,"label":1070,"name":1071,"to":1072},"pl","PL","Polish","\u002F",[1074,1189,1255],{"id":1075,"title":1076,"body":1077,"challenge":1142,"client":1053,"description":1143,"extension":41,"features":1144,"meta":1151,"navigation":61,"order":62,"path":1152,"relatedServices":1153,"results":1154,"screenshotDesktop":1057,"screenshotMobile":1158,"seo":1159,"sequence":1160,"sitemap":1163,"slug":91,"solution":1170,"stack":1171,"stem":1176,"summary":1056,"tag":1054,"url":1177,"usedBy":1178,"year":1055,"__hash__":1188},"caseStudiesEn\u002Fcase-studies\u002Fdss-by-caredo.md","DSS by Caredo — a product we build together with the Caredo team",{"type":12,"value":1078,"toc":1136},[1079,1083,1086,1089,1093,1109,1116,1120,1123,1127],[15,1080,1082],{"id":1081},"starting-point","Starting point",[20,1084,1085],{},"DSS (Digital Service Station) is a system for car dealerships and service centres that takes the customer from the moment they pull into the car park to the moment they collect their car. A totem greets them and shows them where to park, a key locker takes the key without the front desk, a parts dispenser hands a mechanic the parts for a specific work order.",[20,1087,1088],{},"Each of those devices only makes sense if it knows who the customer is and which work order is in progress. That is the software's job — and that is the part we build together with Caredo.",[15,1090,1092],{"id":1091},"what-we-build-together","What we build together",[20,1094,1095,1096,1100,1101,1104,1105,1108],{},"A ",[1097,1098,1099],"strong",{},"CRM"," where the customer, their history and their work orders are one record. A ",[1097,1102,1103],{},"planner"," where the schedule of visits and work orders is made. A ",[1097,1106,1107],{},"key handover system",": the customer drops off or collects a key at any hour, and the system assigns it to the work order and logs every operation on its own.",[20,1110,1111,1112,1115],{},"On top of that, ",[1097,1113,1114],{},"device integrations"," — external and internal key lockers, the parts dispenser, the tool dispenser and the parking totem — so that each one is part of a single process rather than a separate machine with its own database.",[15,1117,1119],{"id":1118},"device-interfaces-for-brands","Device interfaces for brands",[20,1121,1122],{},"A Porsche customer shouldn't see the same key-locker screen as a Kia customer. For Mercedes-Benz, Porsche, Toyota and Kia dealers we build device interfaces in each brand's identity — screens the customer uses alone, with no member of staff beside them, so they have to make sense from the first touch.",[15,1124,1126],{"id":1125},"how-we-work-together","How we work together",[20,1128,1129,1130,1135],{},"We're not the vendor of a single module. We work with the Caredo team on the whole product: when a new device is designed, its software and its integration with the rest of the system are built alongside it, not after the fact. The product website, dssbycaredo.com, we built separately — it's a ",[1131,1132,1134],"a",{"href":1133},"\u002Fen\u002Fcase-studies\u002Fdss-by-caredo-website","separate case study",".",{"title":34,"searchDepth":35,"depth":35,"links":1137},[1138,1139,1140,1141],{"id":1081,"depth":38,"text":1082},{"id":1091,"depth":38,"text":1092},{"id":1118,"depth":38,"text":1119},{"id":1125,"depth":38,"text":1126},"Caredo designs devices for dealerships and service centres: key lockers, parts dispensers, parking totems. The hardware is half the product. The other half is the software that connects each device to the customer, the work order and the service team — and that has to look like the brand's showroom, not like a technical panel.","Together with the Caredo team we build the whole DSS product: the CRM, the planner, the key handover system, the integrations of the devices on site and the device interfaces for Mercedes-Benz, Porsche, Toyota and Kia dealers.",[1145,1146,1147,1148,1149,1150],"A CRM with customer history, work orders and permissions per branch and role","A planner for visits and service orders","A 24\u002F7 key drop-off and pickup system that assigns each key to its work order","Integrations for the key lockers, parts and tool dispensers and the parking totem","Customer-facing device interfaces in Mercedes-Benz, Porsche, Toyota and Kia identity","An analytics dashboard with real-time data",{},"\u002Fcase-studies\u002Fdss-by-caredo",[118,327,519],[1155],{"metric":1156,"label":1157},"100%","System uptime",null,{"title":1076,"description":1143},{"path":1161,"frames":1162,"poster":1057},"\u002Fimg\u002Fcase-studies\u002Fdss\u002Fkluczykomat\u002Fframe_",169,{"loc":1164,"alternatives":1165},"\u002Fen\u002Fcase-studies\u002Fdss-by-caredo",[1166,1168,1169],{"hreflang":112,"href":1167},"\u002Frealizacje\u002Fdss-by-caredo",{"hreflang":115,"href":1167},{"hreflang":117,"href":1164},"We work as part of the Caredo team: together we build the CRM, the planner, the key drop-off and pickup system and the integrations that bring every device into one system. For Mercedes-Benz, Porsche, Toyota and Kia dealers we design device interfaces in each brand's identity.",[1172,1173,1174,1175],"TypeScript","Nuxt","Node.js","PostgreSQL","case-studies\u002Fdss-by-caredo","https:\u002F\u002Fdssbycaredo.com",[1179,1180,1181,1182,1183,1184,1185,1186,1187],"Mercedes-Benz","Porsche","Toyota","Kia","Audi","Cupra","Ford","Škoda","Volkswagen","MS9XoW0yDSBUBi4JOZJ4VQn87W5x7rIKYo99PuI8oSg",{"id":1190,"title":1191,"body":1192,"challenge":1222,"client":1053,"description":1223,"extension":41,"features":1224,"meta":1231,"navigation":61,"order":38,"path":1232,"relatedServices":1233,"results":1234,"screenshotDesktop":1062,"screenshotMobile":1158,"seo":1241,"sequence":1158,"sitemap":1242,"slug":1059,"solution":1248,"stack":1249,"stem":1252,"summary":1061,"tag":1060,"url":1177,"usedBy":1253,"year":1055,"__hash__":1254},"caseStudiesEn\u002Fcase-studies\u002Fdss-by-caredo-website.md","dssbycaredo.com — the DSS product website, built on Caredo's identity",{"type":12,"value":1193,"toc":1218},[1194,1196,1199,1203,1206,1209,1212],[15,1195,1082],{"id":1081},[20,1197,1198],{},"Caredo had a finished visual identity and a product that's hard to show in one photo: DSS is several devices plus the software that makes them work as one system. The website had to explain that to a dealer in a few scrolls.",[15,1200,1202],{"id":1201},"what-we-did","What we did",[20,1204,1205],{},"The whole site — design and build — on Caredo's identity. The story runs from what DSS is, through why a dealership needs it, to a diagram showing where each device stands on the floor and what it connects to.",[20,1207,1208],{},"The devices aren't photos: each is a frame sequence drawn on a canvas and moved by scrolling, so the key locker opens and turns as the visitor scrolls down — 958 frames across four devices.",[20,1210,1211],{},"The IPS section's video is served in three formats and three resolutions, so a phone on a weak connection doesn't download the same file as a 4K monitor. Every path through the page ends in the same place: a call-back form where the dealer ticks what they want to talk about.",[20,1213,1214,1215,1217],{},"The DSS product itself — the CRM, the planner, the device integrations — is a ",[1131,1216,1134],{"href":1164},", one we build together with the Caredo team.",{"title":34,"searchDepth":35,"depth":35,"links":1219},[1220,1221],{"id":1081,"depth":38,"text":1082},{"id":1201,"depth":38,"text":1202},"DSS isn't one device, it's a whole system: a totem, key lockers, a parts dispenser and the software that connects them. The website had to show how those pieces work together on a dealership floor, fit Caredo's existing visual identity and take a dealer straight to a conversation with sales.","We designed and built the DSS product website end to end on Caredo's visual identity: devices shown as scroll-driven frame sequences, an animated system diagram and call-back forms.",[1225,1226,1227,1228,1229,1230],"Design and build in Caredo's visual identity","Devices as frame sequences played by scrolling (canvas, GSAP)","An animated diagram of the DSS system on a dealership floor","Video in AV1, WebM and MP4, at 480p, 720p and 1080p","Call-back forms with a choice of topic","Structured data and social link previews",{},"\u002Fcase-studies\u002Fdss-by-caredo-website",[622],[1235,1238],{"metric":1236,"label":1237},"958","Frames in the scroll-driven sequences of four devices",{"metric":1239,"label":1240},"3 × 3","Video formats and resolutions — matched to the device",{"title":1191,"description":1223},{"loc":1133,"alternatives":1243},[1244,1246,1247],{"hreflang":112,"href":1245},"\u002Frealizacje\u002Fstrona-dss-by-caredo",{"hreflang":115,"href":1245},{"hreflang":117,"href":1133},"We designed and built the site on Caredo's identity: a story from \"what is DSS\" to contact, an animated diagram of the system on a dealership floor, an IPS section with video and four devices that turn and open as the page scrolls. Contact is a call-back form with a choice of topic.",[1173,1250,1251,1172],"Vue","GSAP","case-studies\u002Fdss-by-caredo-website",[],"V9NwZH0sBE-rqK_K2GBXnPZgMIFEFoJhcWC5cbvAkc8",{"id":1256,"title":1257,"body":1258,"challenge":1288,"client":493,"description":1289,"extension":41,"features":1290,"meta":1296,"navigation":61,"order":35,"path":1297,"relatedServices":1298,"results":1299,"screenshotDesktop":1066,"screenshotMobile":1308,"seo":1309,"sequence":1158,"sitemap":1310,"slug":493,"solution":1317,"stack":1318,"stem":1320,"summary":1065,"tag":1064,"url":1321,"usedBy":1322,"year":1055,"__hash__":1323},"caseStudiesEn\u002Fcase-studies\u002F2motion.md","2motion — the whole brand, website and blog for industrial automation",{"type":12,"value":1259,"toc":1283},[1260,1262,1265,1268,1270,1273,1276,1280],[15,1261,1082],{"id":1081},[20,1263,1264],{},"An engineering company has a harder job than a shop: it sells expertise, not a product you can photograph. The site has to convince a technical visitor within seconds that there are people on the other end who know what they're doing.",[20,1266,1267],{},"On top of that: the client often opens the site on a phone, on the shop floor, on a poor connection.",[15,1269,1202],{"id":1201},[20,1271,1272],{},"The brand first: the logo, the colour palette and business cards — 2motion started without an identity, so the website had nothing to stand on. Then a statically generated site where the HTML is ready before anyone arrives. Every subpage is prerendered, images are served in modern formats, and JavaScript only ships where it's actually needed.",[20,1274,1275],{},"The content architecture was decided before the visual design: we first established which subpage answers which query, so they wouldn't compete against each other in search results. Each of the six services has its own page, and the blog posts we co-write with 2motion answer the questions their clients arrive with from search — from palletising to integrating robots into an existing line.",[15,1277,1279],{"id":1278},"what-we-learned","What we learned",[20,1281,1282],{},"On a brand site, the decision with the biggest impact on the outcome isn't visible in the design — it's how much content actually gets written. A layout for eight paragraphs and a layout for two are two different projects, and that number is only known once someone sits down to write.",{"title":34,"searchDepth":35,"depth":35,"links":1284},[1285,1286,1287],{"id":1081,"depth":38,"text":1082},{"id":1201,"depth":38,"text":1202},{"id":1278,"depth":38,"text":1279},"A company in industrial automation sells expertise that can't be shown in a product photo. The site needed to build technical credibility, work flawlessly on a phone on a client's shop floor, and rank for industry-specific search terms.","We created 2motion's whole brand — logo, colours, business cards — built its website and co-write the blog posts that build its search visibility.",[1291,1292,1293,1294,1295],"A visual identity from scratch — logo, colours, business cards","A company website with a page for each of six services","A blog with co-written posts aimed at industry search terms","Technical SEO — structured data, sitemap, canonical URLs","Static generation and image optimisation",{},"\u002Fcase-studies\u002F2motion",[622],[1300,1303,1305],{"metric":1301,"label":1302},"6","Service pages, each for its own search term",{"metric":1301,"label":1304},"Blog posts co-written for SEO",{"metric":1306,"label":1307},"\u003C1.2 s","Time to first render","\u002Fimg\u002Fscreenshots\u002F2motion-mobile.jpg",{"title":1257,"description":1289},{"loc":1311,"alternatives":1312},"\u002Fen\u002Fcase-studies\u002F2motion",[1313,1315,1316],{"hreflang":112,"href":1314},"\u002Frealizacje\u002F2motion",{"hreflang":115,"href":1314},{"hreflang":117,"href":1311},"We created the brand from the ground up: the logo, the colour palette and business cards, and on top of them a statically generated website with a page for every service. Together with 2motion we co-write blog posts that answer their clients' questions and build visibility for industry terms.",[1172,1173,1319],"Vercel","case-studies\u002F2motion","https:\u002F\u002F2motion.pl",[],"P9NX81zWImOQJrUEvem3RidKuJSGHm2UlrA5z02USqc",{"id":1325,"title":1326,"body":1327,"description":1361,"extension":41,"faq":1362,"heroHeadline":1375,"heroSubline":1376,"meta":1377,"navigation":61,"path":1378,"seo":1379,"stem":1380,"steps":1381,"__hash__":1401},"howWeWorkEn\u002Fen\u002Fcompany\u002Fhow-we-work.md","How we work — our delivery process",{"type":12,"value":1328,"toc":1356},[1329,1333,1336,1339,1343,1346,1349,1353],[15,1330,1332],{"id":1331},"why-iterations-rather-than-a-single-delivery-date","Why iterations rather than a single delivery date",[20,1334,1335],{},"The most expensive mistake in a software project is a misunderstanding that surfaces after three months. It costs not what the fix costs, but what everything built on top of it costs.",[20,1337,1338],{},"Two weeks is the shortest period in which something working can be delivered, and the longest worth waiting to have an assumption checked. A version on staging isn't a progress report — it's evidence you can click, and say \"that isn't what I meant\", before three more features are built on top of it.",[15,1340,1342],{"id":1341},"what-we-need-from-you","What we need from you",[20,1344,1345],{},"One person who can make decisions and has two hours a month. Not to supervise the code — to settle the questions we can't answer, because they are about how your company works, not about how software works.",[20,1347,1348],{},"Access to the people who do the process by hand today. They are the ones who know the exceptions that appear in no procedure and still have to exist in the system.",[15,1350,1352],{"id":1351},"what-we-dont-do","What we don't do",[20,1354,1355],{},"We don't start building without a workshop. We don't quote a project off a one-hour conversation — that number is guesswork in a PDF and falls apart on contact with reality. We don't promise deadlines we don't believe in ourselves.",{"title":34,"searchDepth":35,"depth":35,"links":1357},[1358,1359,1360],{"id":1331,"depth":38,"text":1332},{"id":1341,"depth":38,"text":1342},{"id":1351,"depth":38,"text":1352},"Five stages from the first call to launch. How long each takes, what happens in it, and what you are left holding at the end — including if you decide to build with someone else.",[1363,1366,1369,1372],{"q":1364,"a":1365},"Can I walk away after the discovery workshop?","Yes, and people regularly do. The scope, timeline and quote are yours — take them to another vendor or to your board for budget. The workshop is paid precisely so that decision stays free.",{"q":1367,"a":1368},"What happens if the scope changes mid-build?","Scope changing is normal; pretending it won't is not. On fixed price a change goes through a written amendment with its own quote; on time and material it simply enters the next iteration. That is why the quote states its assumptions — so it is clear which one has just stopped holding.",{"q":1370,"a":1371},"Who writes the code — the person I'm talking to?","Yes. We are a small team and stay that way deliberately, so the person in the first meeting is the one who later writes the code. There is no account manager who hands the project on.",{"q":1373,"a":1374},"What if we stop working together halfway?","You keep what has been built. The repository, the rights and the infrastructure are on your accounts from the start, and documentation and tests are written so another team can take over without us. That is a condition of fair collaboration, not a favour.","A process where you can see what was built at every stage","We don't disappear for three months and come back with a finished system. After every two-week cycle there is a version you can click through — even when it doesn't do much yet.",{},"\u002Fen\u002Fcompany\u002Fhow-we-work",{"title":1326,"description":1361},"en\u002Fcompany\u002Fhow-we-work",[1382,1387,1390,1393,1397],{"step":1383,"duration":1384,"deliverable":1385,"body":1386},"The call","one hour, free","An answer on whether we are the right vendor","We ask about the process you want to fix: who does it today, how many hours it eats, and where it breaks most often. We don't talk about a solution until we understand the problem. Sometimes this ends with us saying an off-the-shelf tool and two integrations would do — and we say it, even though in the short term that costs us the work.",{"step":76,"duration":77,"deliverable":1388,"body":1389},"Scope, timeline and a quote with its assumptions stated","A paid stage, and the only one that leaves you with material you can put in front of other vendors. We map the process, agree what belongs in the first version and write down what is deliberately deferred. The quote gives not just a number but the assumptions it rests on and what would change it — so a change order is never a surprise.",{"step":80,"duration":81,"deliverable":1391,"body":1392},"A clickable prototype of the key screens","Before any code exists, there is a prototype you can walk through as if it were the finished application. This is the cheapest moment to change your mind: a fix in the prototype costs hours, the same fix after launch costs weeks.",{"step":1394,"duration":85,"deliverable":1395,"body":1396},"Build in iterations","A working version on staging every two weeks","Two-week cycles. At the end of each there is a version on staging that you have had access to since day one. There is no stage where you have to take our word for it — progress is something you can see, not something described in a report.",{"step":1398,"duration":89,"deliverable":1399,"body":1400},"Launch and support","Data migration, team training and monitoring","Moving data off the old system, training, switching monitoring on. The project doesn't end on launch day — it ends when the team is working in the new system and nobody goes back to the spreadsheet.","TgjQqeJJk-YTGqhXdpgLzAypV1-xUBGNJIk1ykLvjOM",[],[1404,1678,1965],{"id":1405,"title":1406,"author":1407,"body":1408,"category":1662,"date":1663,"description":1664,"draft":1665,"editorialNote":1158,"extension":41,"image":1666,"meta":1667,"navigation":61,"path":1668,"rawbody":1669,"seo":1670,"sitemap":1671,"stem":1672,"tags":1673,"translationKey":1676,"updated":1158,"__hash__":1677},"blogEn\u002Fblog\u002Fdedykowany-erp-czy-gotowy-system.md","Dedicated ERP or off-the-shelf — how to choose","zespol",{"type":12,"value":1409,"toc":1649},[1410,1417,1420,1424,1429,1432,1436,1439,1443,1446,1450,1453,1457,1460,1554,1561,1565,1584,1587,1591,1597,1600,1603,1607,1613,1619,1625,1629,1632,1639,1646],[20,1411,1412,1413,1416],{},"The answer is: ",[1097,1414,1415],{},"off-the-shelf, in most cases",". Worth stating up front, since a piece written by a company that builds dedicated systems might be expected to argue the opposite.",[20,1418,1419],{},"An off-the-shelf ERP wins when your process resembles other companies' in the industry and the budget is limited. Licence plus rollout is then cheaper than building, and the risk is lower. A dedicated system makes sense in a narrower set of situations — and this piece is about recognising when you're in that set.",[15,1421,1423],{"id":1422},"four-deciding-questions","Four deciding questions",[1425,1426,1428],"h3",{"id":1427},"_1-is-your-process-a-source-of-advantage","1. Is your process a source of advantage?",[20,1430,1431],{},"If a company makes money because it does something differently from its competitors, flattening that \"differently\" into a standard module costs more than the licence. If, on the other hand, the process is standard and the advantage lies elsewhere — relationships, price, location — an off-the-shelf system is the right choice.",[1425,1433,1435],{"id":1434},"_2-what-does-adapting-the-off-the-shelf-system-cost","2. What does adapting the off-the-shelf system cost?",[20,1437,1438],{},"This question settles it most often. Ask the vendor for a quote on the modifications you need. If the sum of licence, rollout and modifications approaches the cost of building your own system, the choice stops being obvious — because for the same money you get either an 80%-fit system, or a 100%-fit one.",[1425,1440,1442],{"id":1441},"_3-how-many-users-do-you-have","3. How many users do you have?",[20,1444,1445],{},"A per-user licence changes the maths over time. At twenty people the difference is negligible. At two hundred, over a five-year horizon, it can exceed the cost of building your own system.",[1425,1447,1449],{"id":1448},"_4-how-much-will-the-process-change","4. How much will the process change?",[20,1451,1452],{},"A company in a stable industry, doing the same thing for a decade, fits well into an off-the-shelf system. A company changing its business model every two years will keep fighting limitations that can't be worked around except through the vendor.",[15,1454,1456],{"id":1455},"the-five-year-comparison","The five-year comparison",[20,1458,1459],{},"Comparing only the rollout cost is misleading. Below is an example for a manufacturing company with 120 users. The figures are illustrative — meant to show the cost structure, not a quote.",[1461,1462,1463,1479],"table",{},[1464,1465,1466],"thead",{},[1467,1468,1469,1473,1476],"tr",{},[1470,1471,1472],"th",{},"Line item",[1470,1474,1475],{},"Off-the-shelf ERP",[1470,1477,1478],{},"Dedicated",[1480,1481,1482,1494,1505,1516,1526,1537],"tbody",{},[1467,1483,1484,1488,1491],{},[1485,1486,1487],"td",{},"Rollout \u002F build",[1485,1489,1490],{},"PLN 250k",[1485,1492,1493],{},"PLN 450k",[1467,1495,1496,1499,1502],{},[1485,1497,1498],{},"Licences over 5 years",[1485,1500,1501],{},"PLN 430k",[1485,1503,1504],{},"0",[1467,1506,1507,1510,1513],{},[1485,1508,1509],{},"Modifications and extensions",[1485,1511,1512],{},"PLN 180k",[1485,1514,1515],{},"PLN 150k",[1467,1517,1518,1520,1523],{},[1485,1519,867],{},[1485,1521,1522],{},"PLN 120k",[1485,1524,1525],{},"PLN 220k",[1467,1527,1528,1531,1534],{},[1485,1529,1530],{},"Infrastructure",[1485,1532,1533],{},"included in licence",[1485,1535,1536],{},"PLN 90k",[1467,1538,1539,1544,1549],{},[1485,1540,1541],{},[1097,1542,1543],{},"Total",[1485,1545,1546],{},[1097,1547,1548],{},"PLN 980k",[1485,1550,1551],{},[1097,1552,1553],{},"PLN 910k",[20,1555,1556,1557,1560],{},"The takeaway isn't \"dedicated is cheaper.\" It's: ",[1097,1558,1559],{},"at this scale the costs converge, so the decision should be made on a different basis than price",". At thirty users the same table looks completely different, and the off-the-shelf system wins outright.",[15,1562,1564],{"id":1563},"signals-that-an-off-the-shelf-system-has-stopped-fitting","Signals that an off-the-shelf system has stopped fitting",[1566,1567,1568,1572,1575,1578,1581],"ul",{},[1569,1570,1571],"li",{},"The team keeps the \"real\" data in a spreadsheet next to the system.",[1569,1573,1574],{},"A key report is produced by exporting to Excel and stitching it together by hand.",[1569,1576,1577],{},"Every process change requires a ticket to the vendor and waits for quarters.",[1569,1579,1580],{},"You're paying for modules nobody ever turned on.",[1569,1582,1583],{},"A new hire is learning less the system than the list of workarounds the team invented.",[20,1585,1586],{},"One of these signals is normal friction. Three or more mean the cost of the mismatch has exceeded the cost of change.",[15,1588,1590],{"id":1589},"a-third-path-thats-rarely-discussed","A third path that's rarely discussed",[20,1592,1593,1594,1135],{},"The choice isn't binary. A common and underrated approach is to ",[1097,1595,1596],{},"keep an off-the-shelf ERP as the finance-and-accounting core and build your own modules where the company is genuinely atypical",[20,1598,1599],{},"Accounting, HR and payroll are regulated areas where an in-house build is an expense with no return — the rules change every year and someone has to keep up. A production module, or handling a specific sales channel, is exactly where a custom fit pays off.",[20,1601,1602],{},"The condition is an ERP with a decent API. Without one, this path is closed — and that's an important criterion in choosing an off-the-shelf system that almost nobody asks about before signing.",[15,1604,1606],{"id":1605},"what-not-to-weigh-in-the-decision","What not to weigh in the decision",[20,1608,1609,1612],{},[1097,1610,1611],{},"\"Everyone in the industry has X.\""," Your competitors made that decision at a different scale, in a different year, with a different process.",[20,1614,1615,1618],{},[1097,1616,1617],{},"The sales demo."," Every system looks good in a demo the vendor prepared. Ask for access to a test environment and run your own real case through it — ideally the most unusual one you have.",[20,1620,1621,1624],{},[1097,1622,1623],{},"The promise that \"it'll get configured.\""," Ask who will configure it, how long it'll take, and what a consultant's day costs. The answers are sometimes surprising.",[15,1626,1628],{"id":1627},"how-to-make-this-decision-properly","How to make this decision properly",[20,1630,1631],{},"Do two things before you choose.",[20,1633,1634,1635,1638],{},"First: ",[1097,1636,1637],{},"write down your process as it actually is",", workarounds included. Those workarounds are information about what the previous tool was missing — and the best material for testing candidates.",[20,1640,1641,1642,1645],{},"Second: ",[1097,1643,1644],{},"ask both types of vendor to quote the same, written-down scope",". As long as one is quoting a licence and the other a build, the offers aren't comparable.",[20,1647,1648],{},"Only once you have both of those does the \"dedicated or off-the-shelf\" conversation stop being a matter of opinion and become a calculation.",{"title":34,"searchDepth":35,"depth":35,"links":1650},[1651,1657,1658,1659,1660,1661],{"id":1422,"depth":38,"text":1423,"children":1652},[1653,1654,1655,1656],{"id":1427,"depth":35,"text":1428},{"id":1434,"depth":35,"text":1435},{"id":1441,"depth":35,"text":1442},{"id":1448,"depth":35,"text":1449},{"id":1455,"depth":38,"text":1456},{"id":1563,"depth":38,"text":1564},{"id":1589,"depth":38,"text":1590},{"id":1605,"depth":38,"text":1606},{"id":1627,"depth":38,"text":1628},"erp","2026-09-02","Decision criteria, a five-year cost comparison, and the signals that tell you an off-the-shelf ERP has stopped fitting your company.",false,"\u002Fimg\u002Fblog\u002Ferp-dedykowany-czy-gotowy.jpg",{},"\u002Fblog\u002Fdedykowany-erp-czy-gotowy-system","---\ntitle: Dedicated ERP or off-the-shelf — how to choose\ndescription: Decision criteria, a five-year cost comparison, and the signals that tell you an off-the-shelf ERP has stopped fitting your company.\ndate: 2026-09-02\ncategory: erp\ntags:\n  - erp\n  - rollouts\n  - decisions\nauthor: zespol\nimage: \u002Fimg\u002Fblog\u002Ferp-dedykowany-czy-gotowy.jpg\ntranslationKey: custom-erp-or-off-the-shelf\ndraft: false\n---\n\nThe answer is: **off-the-shelf, in most cases**. Worth stating up front, since a piece written by a company that builds dedicated systems might be expected to argue the opposite.\n\nAn off-the-shelf ERP wins when your process resembles other companies' in the industry and the budget is limited. Licence plus rollout is then cheaper than building, and the risk is lower. A dedicated system makes sense in a narrower set of situations — and this piece is about recognising when you're in that set.\n\n## Four deciding questions\n\n### 1. Is your process a source of advantage?\n\nIf a company makes money because it does something differently from its competitors, flattening that \"differently\" into a standard module costs more than the licence. If, on the other hand, the process is standard and the advantage lies elsewhere — relationships, price, location — an off-the-shelf system is the right choice.\n\n### 2. What does adapting the off-the-shelf system cost?\n\nThis question settles it most often. Ask the vendor for a quote on the modifications you need. If the sum of licence, rollout and modifications approaches the cost of building your own system, the choice stops being obvious — because for the same money you get either an 80%-fit system, or a 100%-fit one.\n\n### 3. How many users do you have?\n\nA per-user licence changes the maths over time. At twenty people the difference is negligible. At two hundred, over a five-year horizon, it can exceed the cost of building your own system.\n\n### 4. How much will the process change?\n\nA company in a stable industry, doing the same thing for a decade, fits well into an off-the-shelf system. A company changing its business model every two years will keep fighting limitations that can't be worked around except through the vendor.\n\n## The five-year comparison\n\nComparing only the rollout cost is misleading. Below is an example for a manufacturing company with 120 users. The figures are illustrative — meant to show the cost structure, not a quote.\n\n| Line item | Off-the-shelf ERP | Dedicated |\n|---|---|---|\n| Rollout \u002F build | PLN 250k | PLN 450k |\n| Licences over 5 years | PLN 430k | 0 |\n| Modifications and extensions | PLN 180k | PLN 150k |\n| Maintenance and support | PLN 120k | PLN 220k |\n| Infrastructure | included in licence | PLN 90k |\n| **Total** | **PLN 980k** | **PLN 910k** |\n\nThe takeaway isn't \"dedicated is cheaper.\" It's: **at this scale the costs converge, so the decision should be made on a different basis than price**. At thirty users the same table looks completely different, and the off-the-shelf system wins outright.\n\n## Signals that an off-the-shelf system has stopped fitting\n\n- The team keeps the \"real\" data in a spreadsheet next to the system.\n- A key report is produced by exporting to Excel and stitching it together by hand.\n- Every process change requires a ticket to the vendor and waits for quarters.\n- You're paying for modules nobody ever turned on.\n- A new hire is learning less the system than the list of workarounds the team invented.\n\nOne of these signals is normal friction. Three or more mean the cost of the mismatch has exceeded the cost of change.\n\n## A third path that's rarely discussed\n\nThe choice isn't binary. A common and underrated approach is to **keep an off-the-shelf ERP as the finance-and-accounting core and build your own modules where the company is genuinely atypical**.\n\nAccounting, HR and payroll are regulated areas where an in-house build is an expense with no return — the rules change every year and someone has to keep up. A production module, or handling a specific sales channel, is exactly where a custom fit pays off.\n\nThe condition is an ERP with a decent API. Without one, this path is closed — and that's an important criterion in choosing an off-the-shelf system that almost nobody asks about before signing.\n\n## What not to weigh in the decision\n\n**\"Everyone in the industry has X.\"** Your competitors made that decision at a different scale, in a different year, with a different process.\n\n**The sales demo.** Every system looks good in a demo the vendor prepared. Ask for access to a test environment and run your own real case through it — ideally the most unusual one you have.\n\n**The promise that \"it'll get configured.\"** Ask who will configure it, how long it'll take, and what a consultant's day costs. The answers are sometimes surprising.\n\n## How to make this decision properly\n\nDo two things before you choose.\n\nFirst: **write down your process as it actually is**, workarounds included. Those workarounds are information about what the previous tool was missing — and the best material for testing candidates.\n\nSecond: **ask both types of vendor to quote the same, written-down scope**. As long as one is quoting a licence and the other a build, the offers aren't comparable.\n\nOnly once you have both of those does the \"dedicated or off-the-shelf\" conversation stop being a matter of opinion and become a calculation.\n",{"title":1406,"description":1664},{"loc":1668},"blog\u002Fdedykowany-erp-czy-gotowy-system",[1662,1674,1675],"rollouts","decisions","custom-erp-or-off-the-shelf","SGZvpSbYxgHfAtuwEdBGzG6HA0KOjIg3dfXrHzqXe4U",{"id":1679,"title":1680,"author":1407,"body":1681,"category":1950,"date":1663,"description":1951,"draft":1665,"editorialNote":1158,"extension":41,"image":1952,"meta":1953,"navigation":61,"path":1954,"rawbody":1955,"seo":1956,"sitemap":1957,"stem":1958,"tags":1959,"translationKey":1963,"updated":1158,"__hash__":1964},"blogEn\u002Fblog\u002File-kosztuje-aplikacja-webowa.md","How much does a dedicated web application cost in 2026",{"type":12,"value":1682,"toc":1941},[1683,1694,1697,1701,1762,1765,1769,1772,1804,1808,1814,1820,1826,1832,1838,1844,1850,1854,1857,1882,1886,1896,1899,1903,1909,1915,1921,1927,1931,1938],[20,1684,1685,1686,1689,1690,1693],{},"A dedicated web application for a company costs, in Poland, anywhere from around ",[1097,1687,1688],{},"PLN 60,000 net"," for a simple internal system to ",[1097,1691,1692],{},"PLN 400,000 and up"," for a platform with multiple roles, integrations and a client portal. That spread isn't vendor indecision — it's that very different projects, differing by an order of magnitude in effort, hide under the same label.",[20,1695,1696],{},"Below I break those numbers down and show exactly what pushes a quote up.",[15,1698,1700],{"id":1699},"price-ranges-by-project-type","Price ranges by project type",[1461,1702,1703,1716],{},[1464,1704,1705],{},[1467,1706,1707,1710,1713],{},[1470,1708,1709],{},"Project type",[1470,1711,1712],{},"Net range",[1470,1714,1715],{},"Time to production",[1480,1717,1718,1729,1740,1751],{},[1467,1719,1720,1723,1726],{},[1485,1721,1722],{},"Internal tool, one process, one role",[1485,1724,1725],{},"PLN 60–90k",[1485,1727,1728],{},"3–4 months",[1467,1730,1731,1734,1737],{},[1485,1732,1733],{},"B2B system with a client portal and several roles",[1485,1735,1736],{},"PLN 120–220k",[1485,1738,1739],{},"5–8 months",[1467,1741,1742,1745,1748],{},[1485,1743,1744],{},"SaaS platform with subscriptions and multi-tenancy",[1485,1746,1747],{},"PLN 250–400k",[1485,1749,1750],{},"8–14 months",[1467,1752,1753,1756,1759],{},[1485,1754,1755],{},"Extending an existing system",[1485,1757,1758],{},"PLN 15–60k per module",[1485,1760,1761],{},"3–10 weeks",[20,1763,1764],{},"These are ranges for a Polish vendor with a senior team, at PLN 160–260 per hour. Offers significantly lower usually mean one of three things: a less experienced team, an underestimated scope, or a model where the gap gets made up in change orders.",[15,1766,1768],{"id":1767},"where-the-money-actually-goes","Where the money actually goes",[20,1770,1771],{},"The cost breakdown for a typical mid-sized project looks like this:",[1566,1773,1774,1780,1786,1792,1798],{},[1569,1775,1776,1779],{},[1097,1777,1778],{},"Analysis and design — 15–20%."," Workshops, the data model, the prototype. The stage where it's easiest to save money and most expensive to have saved it.",[1569,1781,1782,1785],{},[1097,1783,1784],{},"Backend and business logic — 35–40%."," Rules, permissions, integrations, performance.",[1569,1787,1788,1791],{},[1097,1789,1790],{},"Interface — 25–30%."," The more roles and views, the more it costs. The admin panel is sometimes bigger than the client-facing part.",[1569,1793,1794,1797],{},[1097,1795,1796],{},"Testing and rollout — 10–15%."," Environments, release automation, data migration.",[1569,1799,1800,1803],{},[1097,1801,1802],{},"Buffer for the unknown — 10%."," Every project has one. Vendors who don't budget for it make it up in change orders instead.",[15,1805,1807],{"id":1806},"seven-things-that-double-a-quote","Seven things that double a quote",[20,1809,1810,1813],{},[1097,1811,1812],{},"1. Integrations with systems that have no API."," Connecting to a well-documented API takes a few days. Connecting to a system that only offers a file export or direct database access takes weeks — and it's a debt that comes back with every update on that system's side.",[20,1815,1816,1819],{},[1097,1817,1818],{},"2. Migrating data from an inconsistent source."," If a spreadsheet has the same company appearing as \"Smith Ltd\", \"Smith Ltd.\" and \"SMITH LTD\", someone has to resolve that. There's usually more of it than it looks.",[20,1821,1822,1825],{},[1097,1823,1824],{},"3. Offline-first work."," An app that has to work with no connection and sync afterwards needs a local database, an operation queue and conflict-resolution rules. That can turn out to be a third of the whole project.",[20,1827,1828,1831],{},[1097,1829,1830],{},"4. Multilingual support bolted on later."," Adding a second language to a system that wasn't built for it costs several times more than planning for it from the start.",[20,1833,1834,1837],{},[1097,1835,1836],{},"5. A complex permissions model."," The gap between \"admin and user\" and a permissions matrix per module, per field and per branch is weeks of work and a standing cost on every feature after that.",[20,1839,1840,1843],{},[1097,1841,1842],{},"6. Compliance requirements."," Baseline GDPR is cheap. A requirement to audit every data change, retention rules and on-demand anonymisation is a module of its own.",[20,1845,1846,1849],{},[1097,1847,1848],{},"7. An open-ended scope."," The single biggest factor. A project where the scope gets settled along the way ends up costing, in practice, 1.5–2x a project with the same scope described up front.",[15,1851,1853],{"id":1852},"what-a-quote-usually-doesnt-include","What a quote usually doesn't include",[20,1855,1856],{},"Vendors quote the cost of the build. You still need to budget for:",[1566,1858,1859,1865,1870,1876],{},[1569,1860,1861,1864],{},[1097,1862,1863],{},"Maintenance"," — realistically 15–20% of the project's value per year. Monitoring, security updates, small fixes.",[1569,1866,1867,1869],{},[1097,1868,1530],{}," — from a few hundred zloty a month for a simple system to several thousand at higher traffic.",[1569,1871,1872,1875],{},[1097,1873,1874],{},"Content and photography"," — negligible for internal systems, potentially a significant line item for products with a public-facing part.",[1569,1877,1878,1881],{},[1097,1879,1880],{},"Your team's time"," — workshops, acceptance testing, decisions. A few to a dozen hours a week across the whole project. It's a real cost, just not one that shows up on an invoice.",[15,1883,1885],{"id":1884},"how-to-check-whether-a-quote-is-fair","How to check whether a quote is fair",[20,1887,1888,1889,1892,1893,1135],{},"Ask for a breakdown by stage with amounts, and a list of assumptions. A fair quote states not just what's in scope, but also ",[1097,1890,1891],{},"what isn't",", and ",[1097,1894,1895],{},"what happens to the price if an assumption doesn't hold",[20,1897,1898],{},"If you get a single number with no breakdown, you have no way to compare it to another single number. Three offers differing by an order of magnitude almost always mean each of them priced something different.",[15,1900,1902],{"id":1901},"how-to-lower-the-cost-without-lowering-quality","How to lower the cost without lowering quality",[20,1904,1905,1908],{},[1097,1906,1907],{},"Narrow the first rollout to a single process."," A system that handles one process end to end delivers value from day one. A system half-handling five processes delivers none.",[20,1910,1911,1914],{},[1097,1912,1913],{},"Skip configurability you don't need yet."," \"We want to be able to change this later without a developer\" is usually the most expensive sentence in the whole spec.",[20,1916,1917,1920],{},[1097,1918,1919],{},"Use off-the-shelf components where you're not building an advantage."," Authentication, payments, email delivery, search — good components already exist, and writing them from scratch is a cost with no return.",[20,1922,1923,1926],{},[1097,1924,1925],{},"Pay for a workshop before building."," A dozen or so thousand spent closing the scope pays for itself many times over, because it removes the main cause of budget overruns.",[15,1928,1930],{"id":1929},"summary","Summary",[20,1932,1933,1934,1937],{},"If you need one number to open a conversation with the board: ",[1097,1935,1936],{},"an internal system handling one process is around PLN 80,000 net and four months",". Everything above that depends on the number of roles, integrations, and how well the scope is described — not on how many screens the app has.",[20,1939,1940],{},"If you want a number you can defend to the board, you need a workshop on your own data and your own process. That's the only way a quote stops being a guess.",{"title":34,"searchDepth":35,"depth":35,"links":1942},[1943,1944,1945,1946,1947,1948,1949],{"id":1699,"depth":38,"text":1700},{"id":1767,"depth":38,"text":1768},{"id":1806,"depth":38,"text":1807},{"id":1852,"depth":38,"text":1853},{"id":1884,"depth":38,"text":1885},{"id":1901,"depth":38,"text":1902},{"id":1929,"depth":38,"text":1930},"aplikacje-webowe","Real price ranges for web applications, a cost breakdown by stage, and the factors that can double a quote. No \"it depends\" without an explanation.","\u002Fimg\u002Fblog\u002File-kosztuje-aplikacja-webowa.jpg",{},"\u002Fblog\u002File-kosztuje-aplikacja-webowa","---\ntitle: How much does a dedicated web application cost in 2026\ndescription: Real price ranges for web applications, a cost breakdown by stage, and the factors that can double a quote. No \"it depends\" without an explanation.\ndate: 2026-09-02\ncategory: aplikacje-webowe\ntags:\n  - pricing\n  - budget\n  - mvp\nauthor: zespol\nimage: \u002Fimg\u002Fblog\u002File-kosztuje-aplikacja-webowa.jpg\ntranslationKey: cost-of-a-web-application\ndraft: false\n---\n\nA dedicated web application for a company costs, in Poland, anywhere from around **PLN 60,000 net** for a simple internal system to **PLN 400,000 and up** for a platform with multiple roles, integrations and a client portal. That spread isn't vendor indecision — it's that very different projects, differing by an order of magnitude in effort, hide under the same label.\n\nBelow I break those numbers down and show exactly what pushes a quote up.\n\n## Price ranges by project type\n\n| Project type | Net range | Time to production |\n|---|---|---|\n| Internal tool, one process, one role | PLN 60–90k | 3–4 months |\n| B2B system with a client portal and several roles | PLN 120–220k | 5–8 months |\n| SaaS platform with subscriptions and multi-tenancy | PLN 250–400k | 8–14 months |\n| Extending an existing system | PLN 15–60k per module | 3–10 weeks |\n\nThese are ranges for a Polish vendor with a senior team, at PLN 160–260 per hour. Offers significantly lower usually mean one of three things: a less experienced team, an underestimated scope, or a model where the gap gets made up in change orders.\n\n## Where the money actually goes\n\nThe cost breakdown for a typical mid-sized project looks like this:\n\n- **Analysis and design — 15–20%.** Workshops, the data model, the prototype. The stage where it's easiest to save money and most expensive to have saved it.\n- **Backend and business logic — 35–40%.** Rules, permissions, integrations, performance.\n- **Interface — 25–30%.** The more roles and views, the more it costs. The admin panel is sometimes bigger than the client-facing part.\n- **Testing and rollout — 10–15%.** Environments, release automation, data migration.\n- **Buffer for the unknown — 10%.** Every project has one. Vendors who don't budget for it make it up in change orders instead.\n\n## Seven things that double a quote\n\n**1. Integrations with systems that have no API.** Connecting to a well-documented API takes a few days. Connecting to a system that only offers a file export or direct database access takes weeks — and it's a debt that comes back with every update on that system's side.\n\n**2. Migrating data from an inconsistent source.** If a spreadsheet has the same company appearing as \"Smith Ltd\", \"Smith Ltd.\" and \"SMITH LTD\", someone has to resolve that. There's usually more of it than it looks.\n\n**3. Offline-first work.** An app that has to work with no connection and sync afterwards needs a local database, an operation queue and conflict-resolution rules. That can turn out to be a third of the whole project.\n\n**4. Multilingual support bolted on later.** Adding a second language to a system that wasn't built for it costs several times more than planning for it from the start.\n\n**5. A complex permissions model.** The gap between \"admin and user\" and a permissions matrix per module, per field and per branch is weeks of work and a standing cost on every feature after that.\n\n**6. Compliance requirements.** Baseline GDPR is cheap. A requirement to audit every data change, retention rules and on-demand anonymisation is a module of its own.\n\n**7. An open-ended scope.** The single biggest factor. A project where the scope gets settled along the way ends up costing, in practice, 1.5–2x a project with the same scope described up front.\n\n## What a quote usually doesn't include\n\nVendors quote the cost of the build. You still need to budget for:\n\n- **Maintenance** — realistically 15–20% of the project's value per year. Monitoring, security updates, small fixes.\n- **Infrastructure** — from a few hundred zloty a month for a simple system to several thousand at higher traffic.\n- **Content and photography** — negligible for internal systems, potentially a significant line item for products with a public-facing part.\n- **Your team's time** — workshops, acceptance testing, decisions. A few to a dozen hours a week across the whole project. It's a real cost, just not one that shows up on an invoice.\n\n## How to check whether a quote is fair\n\nAsk for a breakdown by stage with amounts, and a list of assumptions. A fair quote states not just what's in scope, but also **what isn't**, and **what happens to the price if an assumption doesn't hold**.\n\nIf you get a single number with no breakdown, you have no way to compare it to another single number. Three offers differing by an order of magnitude almost always mean each of them priced something different.\n\n## How to lower the cost without lowering quality\n\n**Narrow the first rollout to a single process.** A system that handles one process end to end delivers value from day one. A system half-handling five processes delivers none.\n\n**Skip configurability you don't need yet.** \"We want to be able to change this later without a developer\" is usually the most expensive sentence in the whole spec.\n\n**Use off-the-shelf components where you're not building an advantage.** Authentication, payments, email delivery, search — good components already exist, and writing them from scratch is a cost with no return.\n\n**Pay for a workshop before building.** A dozen or so thousand spent closing the scope pays for itself many times over, because it removes the main cause of budget overruns.\n\n## Summary\n\nIf you need one number to open a conversation with the board: **an internal system handling one process is around PLN 80,000 net and four months**. Everything above that depends on the number of roles, integrations, and how well the scope is described — not on how many screens the app has.\n\nIf you want a number you can defend to the board, you need a workshop on your own data and your own process. That's the only way a quote stops being a guess.\n",{"title":1680,"description":1951},{"loc":1954},"blog\u002File-kosztuje-aplikacja-webowa",[1960,1961,1962],"pricing","budget","mvp","cost-of-a-web-application","jhCI0ZJN6yMJqQD2Jbr2XiEVwicPPV8synd3rKHAvg4",{"id":1966,"title":1967,"author":1407,"body":1968,"category":2179,"date":1663,"description":2180,"draft":1665,"editorialNote":1158,"extension":41,"image":2181,"meta":2182,"navigation":61,"path":2183,"rawbody":2184,"seo":2185,"sitemap":2186,"stem":2187,"tags":2188,"translationKey":2190,"updated":1158,"__hash__":2191},"blogEn\u002Fblog\u002Fwdrozenie-ai-w-firmie-od-czego-zaczac.md","AI adoption in your company — where to start",{"type":12,"value":1969,"toc":2169},[1970,1984,1988,1991,1998,2002,2005,2011,2017,2023,2026,2030,2037,2040,2044,2047,2053,2059,2065,2071,2075,2078,2098,2101,2105,2131,2135,2141,2147,2153,2159,2163,2166],[20,1971,1972,1973,1976,1977,1892,1980,1983],{},"Start with a process that meets three conditions at once: it's ",[1097,1974,1975],{},"repetitive",", has a ",[1097,1978,1979],{},"countable time cost",[1097,1981,1982],{},"tolerates a mistake",". Classifying incoming documents usually meets all three. \"An assistant that knows the whole company\" meets none of them — which is why so many rollouts that start there never finish.",[15,1985,1987],{"id":1986},"why-pilots-dont-reach-production","Why pilots don't reach production",[20,1989,1990],{},"A demo shows a model handling a dozen or so examples chosen by the person who prepared them. Production is tens of thousands of examples nobody chose: scans crooked on the glass, documents in a format outside the test set, invoices with a handwritten note in the margin.",[20,1992,1993,1994,1997],{},"The difference between the two isn't model quality. It's ",[1097,1995,1996],{},"handling the cases where the model isn't sure"," — and that's exactly what a rollout is actually made of. A pilot that skips it isn't an earlier version of the rollout. It's a different thing entirely.",[15,1999,2001],{"id":2000},"how-to-choose-your-first-use-case","How to choose your first use case",[20,2003,2004],{},"Make a list of candidates and score each on three dimensions.",[20,2006,2007,2010],{},[1097,2008,2009],{},"Repeatability."," How many times a month does someone do this? Below a hundred, the savings rarely justify a rollout.",[20,2012,2013,2016],{},[1097,2014,2015],{},"Time cost."," How many minutes does one instance take? Multiply by repeatability. That number sets the upper bound on a sensible budget.",[20,2018,2019,2022],{},[1097,2020,2021],{},"Tolerance for error."," What happens if the model gets it wrong? If the answer is \"someone catches it at review\" — good. If it's \"money leaves an account\" — you need a human approval step, which changes the maths.",[20,2024,2025],{},"The best candidates in a typical company: classifying and routing incoming documents, extracting data from invoices and orders, drafting first responses to repetitive support questions, searching internal documentation.",[15,2027,2029],{"id":2028},"set-a-success-metric-before-you-start","Set a success metric before you start",[20,2031,2032,2033],{},"Before a prototype exists, write down one sentence: ",[2034,2035,2036],"em",{},"\"This rollout makes sense if the model handles at least X% of cases on its own, at accuracy of at least Y%.\"",[20,2038,2039],{},"Without that number, there's no way to later decide whether the project succeeded. With it, the prototype ends in a clear decision: proceed, or stop. Stopping is also a good outcome — just a cheaper one than finding out a year in.",[15,2041,2043],{"id":2042},"an-architecture-that-survives-production","An architecture that survives production",[20,2045,2046],{},"A rollout that lasts has four elements a demo doesn't.",[20,2048,2049,2052],{},[1097,2050,2051],{},"A confidence threshold."," The model returns a result along with its own confidence score. Above the threshold, automation runs; below it, the case goes to a human. Setting that threshold is a business decision, not a technical one.",[20,2054,2055,2058],{},[1097,2056,2057],{},"A queue for uncertain cases."," The place where a human resolves cases below the threshold — and its size is the real measure of how well the system is working.",[20,2060,2061,2064],{},[1097,2062,2063],{},"A decision log."," A record of what the model received, what it returned, and with what confidence. Without it you can't diagnose degradation or answer an auditor's question.",[20,2066,2067,2070],{},[1097,2068,2069],{},"Continuous measurement."," Data changes. A model that was 94% accurate in March can be at 80% by November — not because it broke, but because the input stream changed.",[15,2072,2074],{"id":2073},"where-your-data-goes","Where your data goes",[20,2076,2077],{},"The question that comes up in every first meeting, rightly so. You have three options:",[1566,2079,2080,2086,2092],{},[1569,2081,2082,2085],{},[1097,2083,2084],{},"A hosted model, no-training agreement."," Data leaves the company, but the provider commits not to use it for training. Cheapest and fastest, sufficient for most use cases.",[1569,2087,2088,2091],{},[1097,2089,2090],{},"A hosted model in your own private cloud."," Data never leaves your infrastructure. More expensive, justified for sensitive data.",[1569,2093,2094,2097],{},[1097,2095,2096],{},"A model on your own hardware."," Full control, the highest entry and running cost. Makes sense under regulatory requirements that rule out the other options.",[20,2099,2100],{},"The choice is a decision about risk, not technology. You make it once, and it affects cost for the entire lifetime of the solution.",[15,2102,2104],{"id":2103},"what-it-costs","What it costs",[1566,2106,2107,2113,2119,2125],{},[1569,2108,2109,2112],{},[1097,2110,2111],{},"Prototype on your data:"," PLN 15–30k net, 2–3 weeks. Ends with a number you can base a decision on.",[1569,2114,2115,2118],{},[1097,2116,2117],{},"Production rollout:"," PLN 60–200k net, depending on the number of integrations and approval requirements.",[1569,2120,2121,2124],{},[1097,2122,2123],{},"Running the models:"," from a few hundred to a few thousand zloty a month, roughly proportional to volume.",[1569,2126,2127,2130],{},[1097,2128,2129],{},"Maintenance and tuning:"," usually 15% of the rollout's value per year.",[15,2132,2134],{"id":2133},"four-mistakes-that-come-up-most-often","Four mistakes that come up most often",[20,2136,2137,2140],{},[1097,2138,2139],{},"Starting with the most impressive use case."," A conversational assistant impresses the board and is the hardest possible starting point — unbounded scope, no good success metric, high expectations.",[20,2142,2143,2146],{},[1097,2144,2145],{},"No human in the loop."," A system with no path for uncertain cases either performs badly or needs such a high confidence threshold that it only automates a small share of cases.",[20,2148,2149,2152],{},[1097,2150,2151],{},"Measuring accuracy alone."," 95% accuracy sounds great until you work out that at a thousand documents a day, that's fifty errors someone has to catch.",[20,2154,2155,2158],{},[1097,2156,2157],{},"Treating the rollout as a closed project."," A model needs watching, like any other piece of production infrastructure. A rollout with no measurement plan ages quietly.",[15,2160,2162],{"id":2161},"the-first-step-you-can-take-this-week","The first step you can take this week",[20,2164,2165],{},"Pick one process. Count how many times a month it happens and how many minutes it takes. Write down what happens when someone gets it wrong.",[20,2167,2168],{},"Those three numbers are enough to judge whether a prototype is worth building — and they're worth more than a month of conversations about AI's possibilities.",{"title":34,"searchDepth":35,"depth":35,"links":2170},[2171,2172,2173,2174,2175,2176,2177,2178],{"id":1986,"depth":38,"text":1987},{"id":2000,"depth":38,"text":2001},{"id":2028,"depth":38,"text":2029},{"id":2042,"depth":38,"text":2043},{"id":2073,"depth":38,"text":2074},{"id":2103,"depth":38,"text":2104},{"id":2133,"depth":38,"text":2134},{"id":2161,"depth":38,"text":2162},"ai","How to choose your first use case, what it costs, and why most corporate AI projects end at the demo instead of reaching production.","\u002Fimg\u002Fblog\u002Fwdrozenie-ai-w-firmie.jpg",{},"\u002Fblog\u002Fwdrozenie-ai-w-firmie-od-czego-zaczac","---\ntitle: AI adoption in your company — where to start\ndescription: How to choose your first use case, what it costs, and why most corporate AI projects end at the demo instead of reaching production.\ndate: 2026-09-02\ncategory: ai\ntags:\n  - ai\n  - automation\n  - rollouts\nauthor: zespol\nimage: \u002Fimg\u002Fblog\u002Fwdrozenie-ai-w-firmie.jpg\ntranslationKey: ai-adoption-where-to-start\ndraft: false\n---\n\nStart with a process that meets three conditions at once: it's **repetitive**, has a **countable time cost**, and **tolerates a mistake**. Classifying incoming documents usually meets all three. \"An assistant that knows the whole company\" meets none of them — which is why so many rollouts that start there never finish.\n\n## Why pilots don't reach production\n\nA demo shows a model handling a dozen or so examples chosen by the person who prepared them. Production is tens of thousands of examples nobody chose: scans crooked on the glass, documents in a format outside the test set, invoices with a handwritten note in the margin.\n\nThe difference between the two isn't model quality. It's **handling the cases where the model isn't sure** — and that's exactly what a rollout is actually made of. A pilot that skips it isn't an earlier version of the rollout. It's a different thing entirely.\n\n## How to choose your first use case\n\nMake a list of candidates and score each on three dimensions.\n\n**Repeatability.** How many times a month does someone do this? Below a hundred, the savings rarely justify a rollout.\n\n**Time cost.** How many minutes does one instance take? Multiply by repeatability. That number sets the upper bound on a sensible budget.\n\n**Tolerance for error.** What happens if the model gets it wrong? If the answer is \"someone catches it at review\" — good. If it's \"money leaves an account\" — you need a human approval step, which changes the maths.\n\nThe best candidates in a typical company: classifying and routing incoming documents, extracting data from invoices and orders, drafting first responses to repetitive support questions, searching internal documentation.\n\n## Set a success metric before you start\n\nBefore a prototype exists, write down one sentence: *\"This rollout makes sense if the model handles at least X% of cases on its own, at accuracy of at least Y%.\"*\n\nWithout that number, there's no way to later decide whether the project succeeded. With it, the prototype ends in a clear decision: proceed, or stop. Stopping is also a good outcome — just a cheaper one than finding out a year in.\n\n## An architecture that survives production\n\nA rollout that lasts has four elements a demo doesn't.\n\n**A confidence threshold.** The model returns a result along with its own confidence score. Above the threshold, automation runs; below it, the case goes to a human. Setting that threshold is a business decision, not a technical one.\n\n**A queue for uncertain cases.** The place where a human resolves cases below the threshold — and its size is the real measure of how well the system is working.\n\n**A decision log.** A record of what the model received, what it returned, and with what confidence. Without it you can't diagnose degradation or answer an auditor's question.\n\n**Continuous measurement.** Data changes. A model that was 94% accurate in March can be at 80% by November — not because it broke, but because the input stream changed.\n\n## Where your data goes\n\nThe question that comes up in every first meeting, rightly so. You have three options:\n\n- **A hosted model, no-training agreement.** Data leaves the company, but the provider commits not to use it for training. Cheapest and fastest, sufficient for most use cases.\n- **A hosted model in your own private cloud.** Data never leaves your infrastructure. More expensive, justified for sensitive data.\n- **A model on your own hardware.** Full control, the highest entry and running cost. Makes sense under regulatory requirements that rule out the other options.\n\nThe choice is a decision about risk, not technology. You make it once, and it affects cost for the entire lifetime of the solution.\n\n## What it costs\n\n- **Prototype on your data:** PLN 15–30k net, 2–3 weeks. Ends with a number you can base a decision on.\n- **Production rollout:** PLN 60–200k net, depending on the number of integrations and approval requirements.\n- **Running the models:** from a few hundred to a few thousand zloty a month, roughly proportional to volume.\n- **Maintenance and tuning:** usually 15% of the rollout's value per year.\n\n## Four mistakes that come up most often\n\n**Starting with the most impressive use case.** A conversational assistant impresses the board and is the hardest possible starting point — unbounded scope, no good success metric, high expectations.\n\n**No human in the loop.** A system with no path for uncertain cases either performs badly or needs such a high confidence threshold that it only automates a small share of cases.\n\n**Measuring accuracy alone.** 95% accuracy sounds great until you work out that at a thousand documents a day, that's fifty errors someone has to catch.\n\n**Treating the rollout as a closed project.** A model needs watching, like any other piece of production infrastructure. A rollout with no measurement plan ages quietly.\n\n## The first step you can take this week\n\nPick one process. Count how many times a month it happens and how many minutes it takes. Write down what happens when someone gets it wrong.\n\nThose three numbers are enough to judge whether a prototype is worth building — and they're worth more than a month of conversations about AI's possibilities.\n",{"title":1967,"description":2180},{"loc":2183},"blog\u002Fwdrozenie-ai-w-firmie-od-czego-zaczac",[2179,2189,1674],"automation","ai-adoption-where-to-start","3h3Uyc_r6v-R1oggm3sXVR3s8arJjyy0xQy78uryQSg",1790522539699]