[{"data":1,"prerenderedAt":1073},["ShallowReactive",2],{"uslugi-index-en":3,"navigation-en":1018,"language-switcher-\u002Fen\u002Fservices":1067},[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","\u002Fuslugi",1790522539699]