# UiPath Development Services | Gold Partner | Flobotics Canonical: https://www.flobotics.io/uipath-services --- [Home](https://www.flobotics.io/)/[What we do](https://www.flobotics.io/what-we-do)/UiPath Services UiPath Services # Your next UiPath automation shouldn’t start from zero. We’re a UiPath Gold Partner with our own development framework. Each new automation we build for you on the same systems reuses parts of the ones before it, so it costs less to build. We also recommend only the licenses you need. [Book a 30-minute call →](https://tidycal.com/team/flobotics/flobotics-intro-call-w)[What UiPath wrote about us](#proof) - UiPath Gold Partner - Certified UiPath developers - Featured by UiPath FOUR AUTOMATIONS · SAME SYSTEMSEXAMPLE What we build new, and what we reuse 1st2nd3rd4th Login and sessions Moving between screens Screens and fields Error handling and retries Logs and reports Process steps Cost (1st = 100%)100%~55%~40%~25% Built newReused from our library Based on one client’s projects. How much you save depends on how much the processes have in common. Our framework ## We build every automation so the next one can reuse it. The first automation on a system takes the most work: learning the system, handling logins, mapping every screen and field, and deciding what happens when something goes wrong. We build each of those pieces once, as a reusable component. The next automation on the same system reuses them, so we only build what’s different about the new process. [How we structure UiPath projects →](https://www.flobotics.io/blog/naming-conventions-uipath) What goes into our library - Logins and sessions for each system - Moving between screens - Screens and fields, shared between projects - Error handling and retries - Logs and reports - Project structure and naming rules Licenses ## We only recommend the licenses you need. Licenses are a large part of what UiPath costs. Before we recommend any, we look at how much work your robots will do and when your team needs the results. Each robot that runs on its own needs its own license. So we schedule your automations to share robots where they can, and you buy fewer licenses. Our goal is the best return on your automation, not the biggest license order. Robot schedule24 hours Without a plan3 robots Robot 1 Robot 2 Robot 3 With a plan1 robot Robot 1 12 a.m.6 a.m.Noon6 p.m.12 a.m. Eligibility checksClaim status checksPayment posting Illustration. Whether automations can share a robot depends on when your team needs the results. Proof ## UiPath has written about our work and recommended us to a customer. Customer story on uipath.com ### PRMG, a U.S. mortgage lender PRMG’s loan volume was growing faster than its team could handle. We automated six core steps of its loan processing, and UiPath published a customer story about the project. 550tasks automated a day 40 hof manual work saved a day 6:1return on investment “Within very short-term working sessions, they’re able to automate the steps I communicate to them.” PRMG, quoted by UiPath Figures as UiPath reported them at the time. [Read the story on uipath.com ↗](https://www.uipath.com/resources/automation-case-studies/prmg)[Our summary →](https://www.flobotics.io/blog/flobotics-prmg-loan-processing-rpa-automation) Recommended by UiPath ### Docplanner, a platform for booking doctor appointments Docplanner needed to move data between clinics’ EHRs and its app. UiPath built a first version for one EHR and recommended us to build the full system. We rebuilt it from scratch so it could grow to new EHRs, clinics and countries. 10,000+transactions automated a month 10+EHRs connected 4countries [Read the case study →](https://www.flobotics.io/case-studies/docplanner) More of our UiPath work: [SAP automations for a large sugar producer](https://www.flobotics.io/case-studies/sugar-producer-automation), [account activations for Global-View](https://www.flobotics.io/case-studies/global-view-automation), and [denials and payer mail in XiFin, with UiPath and AI](https://www.flobotics.io/case-studies/50k-saved-in-1-month-ai-agent-for-denials-management). Our story ## Why we started Flobotics “Before Flobotics, I worked as an RPA architect at large corporations. What mattered there was how much a project billed, not the quality of what the client got at the end. I didn’t want to work that way, so we started a company where the quality of what the client gets comes first.” Karl MielnickiCo-founder and CTO ## UiPath implementation, support and licensing ### Starting with UiPath We find what’s worth automating and build your first automations. ### Adding more automations Each new automation reuses what we’ve already built for you. ### Paying for too many licenses We check your licenses and tell you what you can stop paying for. ### Robots that keep breaking We fix unreliable robots, including ones another partner built. We also maintain automations as your systems change. [Maintenance and support](https://www.flobotics.io/maintenance-support) ### A dedicated UiPath team Our developers work as part of your team, for as long as you need them. [Dedicated teams](https://www.flobotics.io/dedicated-teams)[Our 30-day promise](https://www.flobotics.io/our-promise) ### Not only UiPath If another tool fits a process better, we’ll tell you. Sometimes a Python script or an API connection does the job without a robot license. We compare the total cost, including maintenance, not only the license price. Talk to us ## Getting the most out of UiPath? Book a 30-minute call with Karl, our CTO. If you’d rather write, send us a message. [Book a 30-minute call →](https://tidycal.com/team/flobotics/flobotics-intro-call-w)[Send us a message](https://www.flobotics.io/contact) 30-minute callKarl MielnickiCo-founder, CTO Show me your robots and your licenses. I’ll tell you what we can build or fix, and where you might be paying for more than you use. Karl