[{"data":1,"prerenderedAt":472},["ShallowReactive",2],{"navigation-en":3,"branze-slug-en-logistics":87,"language-switcher-\u002Fen\u002Findustries\u002Flogistics":467},{"services":4,"industries":48,"caseStudies":69},[5,10,14,19,23,27,31,35,39,43],{"slug":6,"navLabel":7,"navGroup":8,"heroHeadline":9},"web-applications","Web applications","build","A web application built around your process",{"slug":11,"navLabel":12,"navGroup":8,"heroHeadline":13},"erp-systems","ERP systems","An ERP system built for your company, not the other way round",{"slug":15,"navLabel":16,"navGroup":17,"heroHeadline":18},"integrations-and-api","Integrations and APIs","improve","Your systems stop being islands",{"slug":20,"navLabel":21,"navGroup":17,"heroHeadline":22},"ai-implementation","AI implementation","AI deployed where it actually saves time",{"slug":24,"navLabel":25,"navGroup":17,"heroHeadline":26},"process-automation","Process automation","Work no one should be doing by hand",{"slug":28,"navLabel":29,"navGroup":8,"heroHeadline":30},"websites","Websites","A site that loads instantly and brings in inquiries",{"slug":32,"navLabel":33,"navGroup":8,"heroHeadline":34},"mobile-applications","Mobile applications","One codebase, both platforms",{"slug":36,"navLabel":37,"navGroup":17,"heroHeadline":38},"code-audit-and-project-takeover","Code audit and takeover","The project stalled. We'll take it over and tell you the truth about its condition",{"slug":40,"navLabel":41,"navGroup":17,"heroHeadline":42},"maintenance-and-support","Maintenance and support","A system needs someone watching it after launch",{"slug":44,"navLabel":45,"navGroup":46,"heroHeadline":47},"discovery-workshop","Discovery workshop","start","Before you decide to build, find out exactly what you're building",[49,53,57,61,65],{"slug":50,"navLabel":51,"heroHeadline":52},"manufacturing","Manufacturing","The works order reaches the floor as a printout from an email",{"slug":54,"navLabel":55,"heroHeadline":56},"automotive","Automotive","The customer exists in three places at once",{"slug":58,"navLabel":59,"heroHeadline":60},"industrial-automation","Industrial automation","You sell competence that doesn't photograph",{"slug":62,"navLabel":63,"heroHeadline":64},"e-commerce","E-commerce","The shop works. What sits behind it comes apart",{"slug":66,"navLabel":67,"heroHeadline":68},"logistics","Transport and logistics","The job arrives by email, the status comes back by phone",[70,77,82],{"slug":71,"client":72,"tag":73,"year":74,"summary":75,"image":76},"dss-by-caredo","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":78,"client":72,"tag":79,"year":74,"summary":80,"image":81},"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":83,"client":83,"tag":84,"year":74,"summary":85,"image":86},"2motion","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",{"industry":88,"services":179,"relatedCase":151,"i18nSlugs":465},{"id":89,"title":90,"body":91,"description":120,"extension":121,"faq":122,"heroHeadline":68,"heroSubline":132,"keyword":133,"meta":134,"navLabel":67,"navigation":135,"order":136,"path":137,"problems":138,"relatedCase":151,"relatedServices":152,"seo":153,"sitemap":154,"slug":66,"solutions":164,"stem":177,"__hash__":178},"industriesEn\u002Findustries\u002Flogistics.md","Software for transport and logistics companies",{"type":92,"value":93,"toc":113},"minimark",[94,99,103,106,110],[95,96,98],"h2",{"id":97},"where-we-start","Where we start",[100,101,102],"p",{},"By counting phone calls. Genuinely: the number of conversations needed to\nestablish one status is the single best indicator of how much can be recovered\nhere — and the easiest to check before any quote.",[100,104,105],{},"Then with one process, not the whole company. Usually the waybill flow or\ndriver settlements, because that is where manual work is most countable.",[95,107,109],{"id":108},"what-we-dont-promise","What we don't promise",[100,111,112],{},"We don't promise route optimisation that beats an experienced planner. An\nalgorithm handles constraints that can be written down; it handles less well\nthe fact that one particular driver shouldn't be sent to one particular\naddress. We build a tool that suggests and remembers — the decision stays with\nthe person.",{"title":114,"searchDepth":115,"depth":115,"links":116},"",3,[117,119],{"id":97,"depth":118,"text":98},2,{"id":108,"depth":118,"text":109},"The job arrives by email, the status comes back by phone, the settlement happens in a spreadsheet. Systems for transport and warehousing — planning, waybills, driver settlements.","md",[123,126,129],{"q":124,"a":125},"We already have a TMS. Does that mean you have nothing to offer?","Quite the opposite — most often we work alongside an existing TMS. What is usually missing isn't the core but the layer around it: the driver's app, the document flow, or the settlements that get done in a spreadsheet anyway.",{"q":127,"a":128},"Will the driver's app work without signal?","It has to, and that is one of the first requirements we settle. Local storage and syncing once the connection returns is not an extra — it is the condition for anyone using it at all.",{"q":130,"a":131},"How long does it take?","A first working version — usually the job register or the driver's app — after a few weeks. The full scope depends on the number of integrations and how many exceptions your process has; that surfaces in the discovery workshop and is then counted rather than guessed.","In transport, information moves slower than the goods. Usually not because a system is missing, but because the decisions that matter are made in a conversation that is recorded nowhere.","software for transport companies",{},true,5,"\u002Findustries\u002Flogistics",[139,142,145,148],{"title":140,"body":141},"The shipment status lives in the dispatcher's head","The customer calls for an update, the dispatcher calls the driver, then calls back. Three conversations to pass on one date — and no trace at all when, a week later, somebody needs to establish what actually happened.",{"title":143,"body":144},"Waybills circulate as paper and photographs","A signed waybill comes back as a picture in a messaging app. Billing the customer waits on that photo, and finding it a month later is a separate job.",{"title":146,"body":147},"Driver settlements calculated by hand","Mileage, allowances, working time and waiting assembled in a spreadsheet at month end. The error surfaces at payroll, and correcting it means reconstructing a whole route from memory.",{"title":149,"body":150},"Planning rests on one person","Whoever knows the drivers' constraints, the delivery windows and which customer won't accept after three o'clock does the planning. Their absence is an operational risk, not an HR one.",null,[32,15,24],{"title":90,"description":120},{"loc":155,"alternatives":156},"\u002Fen\u002Findustries\u002Flogistics",[157,160,162],{"hreflang":158,"href":159},"x-default","\u002Fbranze\u002Flogistyka",{"hreflang":161,"href":159},"pl-PL",{"hreflang":163,"href":155},"en-US",[165,168,171,174],{"title":166,"body":167},"One register from intake to settlement","The job, its assignment, statuses and documents as a single record. The customer gets an answer without a chain of phone calls, and the history survives after the matter is closed.",{"title":169,"body":170},"Documents attached from the driver's phone","A scan or photograph of the waybill goes straight onto the job, not into a chat thread. Billing stops waiting on somebody's memory.",{"title":172,"body":173},"Settlements calculated from data that already exists","Working time, routes and waiting collected as they happen rather than reconstructed at month end. The spreadsheet survives at most as an export, not as the source.",{"title":175,"body":176},"A mobile app for people in the field","A driver works on a phone, in motion and often on poor signal — a different set of requirements from an office panel. We build in React Native, so one codebase covers iOS and Android.","industries\u002Flogistics","TUNNA4VWLjUo5q7km7CXpkMSxZHuaTiLNnwDTX4Cru4",[180,273,375],{"id":181,"title":182,"audience":183,"body":187,"description":202,"extension":121,"faq":203,"heroHeadline":34,"heroSubline":216,"keyword":217,"meta":218,"navGroup":8,"navLabel":33,"navigation":135,"order":219,"path":220,"pricingModels":221,"process":228,"relatedCase":83,"relatedPosts":245,"scope":247,"seo":263,"sitemap":264,"slug":32,"stem":271,"__hash__":272},"servicesEn\u002Fservices\u002Fmobile-applications.md","Mobile applications for business",[184,185,186],"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":92,"value":188,"toc":199},[189,193,196],[95,190,192],{"id":191},"offline-is-harder-than-it-looks","Offline is harder than it looks",[100,194,195],{},"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.",[100,197,198],{},"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":114,"searchDepth":115,"depth":115,"links":200},[201],{"id":191,"depth":118,"text":192},"We build mobile apps in React Native and Flutter — one codebase, iOS and Android, faster time to launch and cheaper maintenance.",[204,207,210,213],{"q":205,"a":206},"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":208,"a":209},"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":211,"a":212},"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":214,"a":215},"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.","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",{},7,"\u002Fservices\u002Fmobile-applications",[222,225],{"name":223,"body":224},"Fixed price after prototype","Scope is known once the mockup exists, so we can give an amount and a deadline.",{"name":226,"body":227},"Time & material","For products whose shape will keep changing with market feedback.",[229,233,237,241],{"step":230,"duration":231,"body":232},"Scope and technology choice","1 week","What it needs to do, what it runs on, what has to work offline.",{"step":234,"duration":235,"body":236},"Interface prototype","2 weeks","A clickable mockup on-device, tested by the people who'll actually use it.",{"step":238,"duration":239,"body":240},"Build","10–20 weeks","Iterations, with versions available through a test channel.",{"step":242,"duration":243,"body":244},"Launch and growth","ongoing","Release, crash monitoring, further versions.",[246],"ile-kosztuje-aplikacja-webowa",[248,251,254,257,260],{"title":249,"body":250},"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":252,"body":253},"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":255,"body":256},"Device integration","Camera, barcode scanner, GPS, push notifications, biometrics.",{"title":258,"body":259},"App store publishing","We run the process in the App Store and Google Play, including rejections and appeals.",{"title":261,"body":262},"Releases and telemetry","Test channels, crash reporting and usage statistics from the first version onward.",{"title":182,"description":202},{"loc":265,"alternatives":266},"\u002Fen\u002Fservices\u002Fmobile-applications",[267,269,270],{"hreflang":158,"href":268},"\u002Fuslugi\u002Faplikacje-mobilne",{"hreflang":161,"href":268},{"hreflang":163,"href":265},"services\u002Fmobile-applications","vmVbp-gW_e1l-VhWd2VwdXl6lGqV0yPsMi2eyYKqf7M",{"id":274,"title":275,"audience":276,"body":280,"description":303,"extension":121,"faq":304,"heroHeadline":18,"heroSubline":317,"keyword":318,"meta":319,"navGroup":17,"navLabel":16,"navigation":135,"order":115,"path":320,"pricingModels":321,"process":331,"relatedCase":71,"relatedPosts":347,"scope":349,"seo":365,"sitemap":366,"slug":15,"stem":373,"__hash__":374},"servicesEn\u002Fservices\u002Fintegrations-and-api.md","System integrations and APIs",[277,278,279],"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":92,"value":281,"toc":299},[282,286,289,292,296],[95,283,285],{"id":284},"integration-isnt-a-one-off-project","Integration isn't a one-off project",[100,287,288],{},"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.",[100,290,291],{},"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.",[95,293,295],{"id":294},"ksef-without-panic","KSeF without panic",[100,297,298],{},"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":114,"searchDepth":115,"depth":115,"links":300},[301,302],{"id":284,"depth":118,"text":285},{"id":294,"depth":118,"text":295},"We connect ERP, CRM, e-commerce and wholesale systems into one data flow. We implement KSeF and build APIs you can rely on.",[305,308,311,314],{"q":306,"a":307},"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":309,"a":310},"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":312,"a":313},"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":315,"a":316},"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.","The most expensive integration is the one a person performs — copying data from one window to another, every day, with mistakes.","system integration",{},"\u002Fservices\u002Fintegrations-and-api",[322,325,328],{"name":323,"body":324},"Fixed price per integration","A single connection with a known scope — the most common model.",{"name":326,"body":327},"Integration bundle","Several systems at once, quoted together, with a lower rate per additional connection.",{"name":329,"body":330},"SLA retainer","Maintaining working integrations with a guaranteed response time for outages.",[332,336,339,343],{"step":333,"duration":334,"body":335},"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":337,"duration":231,"body":338},"Exchange design","Field mapping, conflict rules, error handling and volumes.",{"step":340,"duration":341,"body":342},"Rollout","2–8 weeks","Depending on the number of systems and whether they expose a reasonable API.",{"step":344,"duration":345,"body":346},"Observation","1 month","We run in production with heightened monitoring before handing off to maintenance.",[348],"ksef-integracja-systemu-firmowego",[350,353,356,359,362],{"title":351,"body":352},"ERP and accounting integrations","Documents, contacts and payments flow automatically, with error handling and a retry queue instead of records silently going missing.",{"title":354,"body":355},"E-commerce and marketplaces","Stock, prices, orders and shipping statuses synced both ways, with conflict resolution.",{"title":357,"body":358},"KSeF rollout","Issuing and receiving structured invoices, authentication, rejection handling and UPO archiving.",{"title":360,"body":361},"Custom APIs","We design and document APIs your partners and clients can plug into without your involvement.",{"title":363,"body":364},"Data exchange monitoring","An alert when synchronisation stops working — before you hear about it from a client.",{"title":275,"description":303},{"loc":367,"alternatives":368},"\u002Fen\u002Fservices\u002Fintegrations-and-api",[369,371,372],{"hreflang":158,"href":370},"\u002Fuslugi\u002Fintegracje-i-api",{"hreflang":161,"href":370},{"hreflang":163,"href":367},"services\u002Fintegrations-and-api","n1j28IOWWWSC0C0MOL_WuQ1u6Fwc7MmprwrJP06AKGM",{"id":376,"title":377,"audience":378,"body":382,"description":397,"extension":121,"faq":398,"heroHeadline":26,"heroSubline":411,"keyword":412,"meta":413,"navGroup":17,"navLabel":25,"navigation":135,"order":136,"path":414,"pricingModels":415,"process":422,"relatedCase":83,"relatedPosts":437,"scope":439,"seo":455,"sitemap":456,"slug":24,"stem":463,"__hash__":464},"servicesEn\u002Fservices\u002Fprocess-automation.md","Business process automation",[379,380,381],"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":92,"value":383,"toc":394},[384,388,391],[95,385,387],{"id":386},"automation-starts-with-a-spreadsheet-of-hours","Automation starts with a spreadsheet of hours",[100,389,390],{},"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.",[100,392,393],{},"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":114,"searchDepth":115,"depth":115,"links":395},[396],{"id":386,"depth":118,"text":387},"We remove repetitive manual work — document flows, reports, retyping data between systems. We start with the process that costs the most hours.",[399,402,405,408],{"q":400,"a":401},"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":403,"a":404},"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":406,"a":407},"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":409,"a":410},"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.","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",{},"\u002Fservices\u002Fprocess-automation",[416,419],{"name":417,"body":418},"Fixed price per process","One process, known scope, known price. The most common and safest model.",{"name":420,"body":421},"Automation retainer","A fixed monthly pool of hours for further automations, for companies that want to go process by process.",[423,426,430,433],{"step":424,"duration":231,"body":425},"Audit and process selection","We review the candidates and pick the one with the best savings-to-difficulty ratio.",{"step":427,"duration":428,"body":429},"Rule design","1–2 weeks","We write down the edge cases and exceptions. They decide success, not the happy path.",{"step":340,"duration":431,"body":432},"2–6 weeks","The automation runs alongside the manual process, so results can be compared.",{"step":434,"duration":435,"body":436},"Switchover and expansion","2–4 weeks","We turn off the manual version and move on to the next process.",[438],"wdrozenie-ai-w-firmie-od-czego-zaczac",[440,443,446,449,452],{"title":441,"body":442},"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":444,"body":445},"Document and approval flows","Requests, orders and invoices with approval rules, reminders and a decision history.",{"title":447,"body":448},"Automatically generated reports","The summaries a person compiles today, built by themselves and delivered wherever they need to land.",{"title":450,"body":451},"Data synchronisation","No more retyping the same record into three systems.",{"title":453,"body":454},"Notifications and escalations","The system watches deadlines instead of a person who has to remember them.",{"title":377,"description":397},{"loc":457,"alternatives":458},"\u002Fen\u002Fservices\u002Fprocess-automation",[459,461,462],{"hreflang":158,"href":460},"\u002Fuslugi\u002Fautomatyzacja-procesow",{"hreflang":161,"href":460},{"hreflang":163,"href":457},"services\u002Fprocess-automation","dWXLPn_QIMw3rILavszqeESlo1LijXwS70wlg6LmA0M",{"pl":466,"en":66},"logistyka",[468],{"code":469,"label":470,"name":471,"to":159},"pl","PL","Polish",1790522545509]