{"message":"success","data":[{"title":"SaaS Development","slug":"saas-development","hasDetail":true,"detail":{"title":"SaaS Development","metaTitle":"SaaS Development Company in Romania, MVP to Launch · RIGTech","summary":"SaaS development for founders and companies: subscriptions, accounts, admin and cloud, from MVP to launch, at a fixed price with the source code handed over.","sections":[{"heading":"In short","body":["RIGTech designs and builds SaaS platforms: web applications customers sign up for and pay for by subscription. We take a product from the first idea through an MVP to launch, including accounts, billing, an admin panel and the cloud setup. The price is fixed in writing before development starts, the people on your first call write the code, and the source code is yours."]},{"heading":"Who this suits","body":["Founders launching a software product, and established businesses turning something they know well into a subscription product. It also suits teams whose first version, often no-code or written in a hurry, has reached its limits.","If you are still deciding what the first version should contain, start with [product strategy and MVP planning](/services/product-strategy)."]},{"heading":"What a SaaS platform needs to work","body":["The feature that makes your product different is usually the smaller part of the build. Around it sits everything a subscription business needs on day one:",["Sign-up, login and password recovery, with roles and permissions for teams.","Multi-tenancy, so each customer sees only their own data.","Subscription billing: plans, trials, card payments, invoices, upgrades and cancellations.","An admin area where you can see your customers and help them.","Email notifications, audit logs and data export.","Hosting, backups and monitoring sized for the customers you have, ready to grow."]]},{"heading":"The technology we use","body":["Usually React and TypeScript in the browser, Node.js on the server and PostgreSQL for the data, with Stripe or a similar provider for subscription billing. These are mainstream choices on purpose: whoever maintains the platform after us, including your own future team, can hire for them easily. If your product has a good reason to need something else, we will say so during planning."]},{"heading":"What affects the price of a SaaS platform","body":[["How many user roles and how much of the product exists in the first version.","Integrations with other tools, such as invoicing, CRM, email or accounting.","How complicated your billing is: flat plans cost less than usage-based pricing.","Compliance needs specific to your industry, on top of GDPR."],"A SaaS platform is priced after a short discovery, then fixed in writing before we build. If the full idea is more than the budget, we cut it to an MVP that can win its first paying customers."]}],"process":{"heading":"How a SaaS project runs","steps":[{"title":"Discovery","body":"We talk through the idea, the customers and how they will pay. You get a written scope, a timeline and a fixed price for the first version."},{"title":"Product design","body":"Screens and flows for the main journey, from sign-up to the moment a customer gets value. You see and change them before any of it is built."},{"title":"MVP development","body":"Accounts, billing and your core feature, with a working build to try every week. Changing direction stays cheap because you see it early."},{"title":"Launch","body":"Production hosting, payments switched to live, monitoring and backups in place, then your first customers on the platform."},{"title":"Growth","body":"Real usage decides what gets built next. You keep talking to the engineers who built it, and you own the code either way."}]},"diagram":{"heading":"How a SaaS platform is put together","caption":"A typical architecture. Each customer has separate data; billing and email are handled by specialised providers rather than rebuilt.","layers":[{"label":"Your users","nodes":["Customer web app","Team accounts and roles","Your admin panel"]},{"label":"Application","nodes":["API","Authentication","Your core features","Background jobs"]},{"label":"Services","nodes":["Subscription billing","Transactional email","File storage","Integrations"]},{"label":"Foundation","nodes":["Multi-tenant database","Backups","Monitoring","Automated deployment"]}]},"faq":[{"question":"How much does it cost to build a SaaS platform?","answer":"It depends on what the first version has to do, so we price it after a short discovery and fix that price in writing before work starts. Cutting the first version to an MVP is the usual way to bring it within budget."},{"question":"What is an MVP, and do I need one?","answer":"A minimum viable product is the smallest version a customer would pay for. For a new product it is usually the right start, because real customers then decide what is worth building next."},{"question":"Who owns the code and the customer data?","answer":"You do. The code is handed over in your own repository, the accounts are in your name, and the customer data is yours."},{"question":"Can you take over an existing SaaS product?","answer":"Yes. We read the code first and tell you honestly what is worth keeping, then quote the changes or the rebuild."},{"question":"Is the platform GDPR compliant?","answer":"We build with GDPR in mind: separated customer data, access control, data export and deletion. Your privacy policy and data processing terms are still your legal responsibility, and we recommend a lawyer reviews them."},{"question":"Can a SaaS platform have a mobile app too?","answer":"Yes. Because everything runs through an API, a [mobile app](/services/mobile-app-development) can be added later without rebuilding the platform."}],"related":[{"label":"Product strategy and MVP planning","path":"/services/product-strategy"},{"label":"Mobile app development","path":"/services/mobile-app-development"},{"label":"Cloud infrastructure and DevOps","path":"/services/cloud-infrastructure"}]}},{"title":"Mobile App Development","slug":"mobile-app-development","hasDetail":true,"detail":{"title":"Mobile App Development","metaTitle":"Mobile App Development, iOS & Android, Romania · RIGTech","summary":"Mobile app development for iOS and Android: design, build, API and store publishing, one codebase, fixed price, with the source code handed over to you.","sections":[{"heading":"In short","body":["RIGTech builds mobile apps for iPhone and Android: the design, the app, the backend behind it and the publishing in the App Store and Google Play. The price is fixed in writing before development starts, you try a test version on your own phone every week, and the source code and store accounts are yours."]},{"heading":"What we build","body":[["Customer apps: accounts, orders, bookings, loyalty and notifications.","Companion apps for an existing website, online shop or SaaS platform.","Internal apps for field teams, deliveries, inspections or stock.","First versions (MVPs) of a new app idea, to test with real users."]]},{"heading":"One app for iOS and Android, or two native ones?","body":["Most business apps do not need two separate codebases. We usually build cross-platform with React Native: one codebase runs on iPhone and Android, which means one budget and one set of changes to maintain.","Fully native development makes sense when the app depends on heavy graphics or deep access to the device. If yours does, we will tell you during planning, before you have paid for the wrong approach."]},{"heading":"What the running costs are","body":["Beyond the build, plan for these, and ask for them in writing with any quote:",["An Apple Developer account, about $99 a year, and a Google Play account, a one-off $25 at the time of writing. Both are in your name.","Hosting for the backend, if the app has accounts or shared data.","Updates when Apple and Google release new system versions, which is a yearly fact of life for any app.","A store commission if you sell digital goods inside the app. Check the current terms for your case."]]},{"heading":"What affects the price of a mobile app","body":[["The number of screens and how much logic sits behind them.","Whether it needs a backend: accounts, shared data and an admin panel.","Device features such as location, camera, Bluetooth, offline mode or push notifications.","Payments and integrations with the systems you already use."],"A mobile app is priced after a short discovery, then fixed in writing before we build."]}],"process":{"heading":"How a mobile app project runs","steps":[{"title":"Discovery","body":"What the app has to do, for whom, and whether an app is the right answer at all. Sometimes a responsive web app does the job for less, and we will say so. You get a written scope, a timeline and a fixed price."},{"title":"UX and UI design","body":"Screens designed for thumbs and small displays, as a clickable prototype you can try on your own phone before anything is built."},{"title":"Development","body":"App and backend built together, with a test version on your phone every week through TestFlight and Google Play testing."},{"title":"Testing and store submission","body":"Tested on real devices, then prepared and submitted to the App Store and Google Play under your accounts, including the review process."},{"title":"Launch and updates","body":"Crash reporting and analytics watch the first real users. Updates for new iOS and Android versions, and new features, come from the people who built it."}]},"diagram":{"heading":"How a mobile app is put together","caption":"A typical setup. The app talks to your backend through an API, so a website or a second app can share the same data.","layers":[{"label":"On the phone","nodes":["iOS app","Android app","Shared React Native code","Offline storage"]},{"label":"Backend","nodes":["API","User accounts","Your business logic","Admin panel"]},{"label":"Services","nodes":["Push notifications","Payments","Maps and location","Integrations"]},{"label":"Foundation","nodes":["Database","File storage","Crash reporting","App Store and Google Play releases"]}]},"faq":[{"question":"How much does it cost to make a mobile app?","answer":"It depends on the screens, the backend and the device features the app uses, so we price it after a short discovery and fix the price in writing before work starts."},{"question":"Do you build for both iOS and Android?","answer":"Yes, usually from one React Native codebase, so both versions share a budget and stay in step. Fully native apps are possible when a project genuinely needs them."},{"question":"Do I need an app, or is a website enough?","answer":"If people use it occasionally and do not need offline use, push notifications or device features, a responsive website or web app is often enough and costs less. We will tell you if that is your case."},{"question":"Do you publish the app in the App Store and Google Play?","answer":"Yes. We prepare and submit it under your own developer accounts, so the listing and the app stay yours."},{"question":"Can an app connect to my existing website or software?","answer":"Usually, yes. If your system has an API we connect to it; if it does not, we can build one. We check this during discovery."},{"question":"Who owns the app and its source code?","answer":"You do. The source code is handed over in your own repository and the store listings are under your accounts."}],"related":[{"label":"SaaS development","path":"/services/saas-development"},{"label":"Custom software development","path":"/services/custom-software"},{"label":"Product strategy and MVP planning","path":"/services/product-strategy"}]}},{"title":"Custom Software Development","slug":"custom-software","hasDetail":true,"detail":{"title":"Custom Software Development","metaTitle":"Custom Software Development in Romania · RIGTech","summary":"Web applications, internal tools and customer portals, quoted at a fixed price before work starts and handed over with the source code.","sections":[{"heading":"What this covers","body":["Software written for how your business actually works, rather than a product you bend your process around. Most of what we build falls into a few shapes:",["Customer-facing web applications: accounts, dashboards, self-service portals.","Internal tools that replace a spreadsheet everyone is afraid of.","Systems that sit between other systems, moving data between tools that were never designed to talk.","Rebuilds of something that works but has become expensive to change."],"If you are not sure which of those describes your situation, that is a normal place to start a conversation from."]},{"heading":"How the work runs","body":["We start by writing down what the software has to do, in language you would use to describe it to a colleague. That document is what we quote against, and it is the reason the price can be fixed rather than estimated hourly.","From there you see working software early and often, not a status report. Each increment is something you can open and use, which is what makes it possible to say \"not quite\" while changing it is still cheap.","The people you meet on the first call are the people who write the code. There is no account layer between you and the work, and no handover to a delivery team you have not met."]},{"heading":"What you have at the end","body":["The running system, the source code, and the ability to leave.",["Full ownership of the code, in your own repository.","Deployment that runs from a command rather than from memory.","Written notes on how it is put together and why, for whoever maintains it next, including if that is not us."],"We would rather be kept because the work is good than because leaving is difficult."]},{"heading":"Who this suits","body":["Businesses whose process is a genuine competitive advantage and does not fit an off-the-shelf product, and teams who have outgrown a tool that was fine at a tenth of the current volume.","It suits you less well if a configured SaaS product would do the job. We will tell you when we think that is the case."]},{"heading":"Custom software people ask us about","body":[["A custom CRM, shaped around how your sales actually work.","ERP-style systems for orders, stock, production or invoicing.","Booking and scheduling systems.","Client portals and B2B web applications.","Integrations and automation between tools you already pay for, such as invoicing, accounting, couriers and email.","Modernising legacy software, or replacing an Excel file that has become the business."]]},{"heading":"Custom software or an off-the-shelf product?","body":["Buy off the shelf when your process is standard: the licence is usually cheaper than a build. Custom software pays for itself when the workaround costs more than the software would, for example hours a week of manual copying, or per-user licences that keep growing with the team. After launch there are no per-user fees to us, and the code is yours."]}],"process":{"heading":"The process, step by step","steps":[{"title":"Discovery","body":"We talk to the people who will use the software and map how the work happens today, including the spreadsheets and the workarounds."},{"title":"Scope and fixed price","body":"A written description of what the software does and what it leaves out, with a timeline and a price that stays fixed."},{"title":"Design and prototype","body":"The main screens, as something you can click through, so misunderstandings surface while they are still free to fix."},{"title":"Development and testing","body":"Working software every week, tested as it is written, on a test environment you can open yourself."},{"title":"Launch and data migration","body":"Your existing data moved across, your team shown how it works, and the old way retired only once the new one holds."},{"title":"Support","body":"Help after launch from the engineers who wrote it, or a clean handover to your own team."}]},"diagram":{"heading":"How custom software fits your business","caption":"A typical web application. It sits between the people doing the work and the tools you already use, so data is entered once.","layers":[{"label":"People","nodes":["Your team","Your customers","Managers and reports"]},{"label":"Application","nodes":["Web interface","API","Roles and permissions","Your business rules"]},{"label":"Your existing tools","nodes":["Invoicing","Accounting","Email","Couriers and suppliers"]},{"label":"Foundation","nodes":["Database","Backups","Monitoring","Automated deployment"]}]},"faq":[{"question":"How much does custom software cost?","answer":"It depends on what it has to do, so there is no honest list price. We run a short discovery, then quote a fixed price in writing against a written scope before any development starts."},{"question":"How long does it take to build custom software?","answer":"It depends on the scope, and you get a written timeline with the fixed price. You see working software every week from the start, rather than waiting for the end."},{"question":"Will I own the source code?","answer":"Yes. Full ownership, in your own repository, with written notes on how it is built, so you are free to continue with any team."},{"question":"Can you integrate it with the software we already use?","answer":"Usually, yes. Most modern tools, including SmartBill and Oblio, offer an API. We check each one during discovery, before we quote."},{"question":"Can you take over or rebuild our old application?","answer":"Yes. We read what exists first, tell you what is worth keeping, and move your data across as part of the work."},{"question":"Do you work with companies outside Romania?","answer":"Yes. We work with clients across the EU, in English and Romanian, and you talk directly to the developers."}],"related":[{"label":"Product strategy and MVP planning","path":"/services/product-strategy"},{"label":"SaaS development","path":"/services/saas-development"},{"label":"Cloud infrastructure and DevOps","path":"/services/cloud-infrastructure"}]}},{"title":"Cloud Infrastructure & DevOps","slug":"cloud-infrastructure","hasDetail":true,"detail":{"title":"Cloud Infrastructure & DevOps","metaTitle":"Cloud Infrastructure Setup & Management · RIGTech","summary":"Hosting, deployment pipelines and monitoring, set up so that releasing a change is uneventful and problems surface before customers find them.","sections":[{"heading":"What this covers","body":["Everything between the code being written and the software being reliably available to the people who use it.",["Hosting sized to real traffic rather than to a worst case nobody has measured.","Deployment pipelines, so a release is a command and not an evening.","Monitoring and alerting that tells you something is wrong before a customer does.","Backups that have actually been restored from, which is the only kind worth having.","Access control, secrets handling and TLS set up properly rather than left at defaults."]]},{"heading":"How the work runs","body":["We start with what you have and what it costs, because cloud bills are usually the fastest thing to improve and the easiest to justify the work with.","Infrastructure is defined in code, not clicked together in a console. That is what makes it reviewable, repeatable, and possible to recreate if a region disappears, and it is why we can hand it over without also having to hand over a person who remembers the clicks.","Changes go out the same way the software does: small, reversible, and observable while they happen."]},{"heading":"What you have at the end","body":["An environment you could rebuild from an empty account, and the documentation to do it.",["The infrastructure definitions, in your repository.","A deployment process any competent engineer can follow.","Dashboards and alerts pointed at the things that actually indicate trouble."]]},{"heading":"Who this suits","body":["Teams whose deployments are manual, tense, or scheduled for a time when nobody is around, and businesses paying for capacity they have never measured.","Also anyone who has inherited an environment that only one person understands, which is a risk long before it is a problem."]},{"heading":"What clients usually come to us for","body":[["Cloud migration, from an old server or shared hosting to something that can grow.","CI/CD pipelines, so tested code reaches production automatically.","Reducing a cloud bill that has quietly grown out of proportion.","Docker containers and infrastructure as code with Terraform.","Uptime monitoring, alerts and centralised logs.","Backups and a disaster recovery plan that has been tested."],"We work with AWS, Google Cloud, Azure and simpler VPS hosting. A small application often does not need a big cloud provider, and we will say so."]}],"process":{"heading":"The process, step by step","steps":[{"title":"Audit","body":"What is running, what it costs and where it could fail: servers, access, backups and the deployment process."},{"title":"Plan and fixed price","body":"A written target setup, the order of the changes and a fixed price, with the savings you can expect stated where they can be estimated."},{"title":"Infrastructure as code","body":"The new environment defined in code and built alongside the old one, so nothing you rely on is touched yet."},{"title":"Migration","body":"Data and traffic moved over in stages, with a tested way back at each stage."},{"title":"Monitoring and handover","body":"Dashboards and alerts in place, a restore from backup actually performed, and documentation your team can follow."}]},"diagram":{"heading":"How a release reaches your users","caption":"A typical setup. Each change goes through the same automated path, and monitoring feeds back what happened.","layers":[{"label":"Delivery","nodes":["Git repository","Automated tests","CI/CD pipeline","Staging environment"]},{"label":"Traffic","nodes":["DNS and CDN","TLS certificates","Load balancer"]},{"label":"Running application","nodes":["Containers","Database","File storage","Secrets management"]},{"label":"Safety net","nodes":["Monitoring and alerts","Central logs","Tested backups","Infrastructure as code"]}]},"faq":[{"question":"Can you reduce our cloud costs?","answer":"Often, yes, especially where capacity was never measured against real traffic. The audit shows what is realistic for your setup before you commit to any further work."},{"question":"Which cloud providers do you work with?","answer":"AWS, Google Cloud, Azure and simpler VPS hosting. We recommend the smallest option that does the job, and the accounts stay in your name."},{"question":"Will the migration cause downtime?","answer":"We plan it to keep downtime as short as possible, usually by building the new environment alongside the old one and moving in stages. If a short window is unavoidable, you will know when, in advance."},{"question":"What is CI/CD, and do we need it?","answer":"CI/CD automatically tests each code change and releases it. If your releases are manual or stressful, it is usually the first thing worth fixing."},{"question":"Do you offer ongoing server administration?","answer":"Yes, it can be agreed as ongoing support after the setup. If you would rather run it yourselves, everything is documented so that your team can."},{"question":"How do you keep our infrastructure secure?","answer":"Least-privilege access, secrets kept out of the code, TLS everywhere, regular updates and tested backups, all reviewable because they are defined in code."}],"related":[{"label":"Custom software development","path":"/services/custom-software"},{"label":"SaaS development","path":"/services/saas-development"},{"label":"Product strategy and MVP planning","path":"/services/product-strategy"}]}},{"title":"Product Strategy & MVP Planning","slug":"product-strategy","hasDetail":true,"detail":{"title":"Product Strategy & MVP Planning","metaTitle":"Product Strategy & MVP Planning · RIGTech","summary":"Deciding what to build before building it: scoping the work, cutting it to something shippable, and putting a fixed price against it.","sections":[{"heading":"What this covers","body":["The work that happens before any code, and that determines whether the code was worth writing.",["Turning a broad ambition into a specific, buildable scope.","Separating what has to exist at launch from what can wait, honestly.","Sizing the work, so the budget conversation happens early rather than at the end.","Mapping how the software fits the process around it, including the parts that stay manual."]]},{"heading":"How the work runs","body":["A short, concentrated engagement rather than a long consultancy. We spend time with the people who will use the thing, not only the people commissioning it, because the gap between those two accounts is where most rework comes from.","The output is a written scope you could hand to any competent team, with the decisions and their reasoning recorded, including the options we rejected, so nobody relitigates them in six months.","It ends with a fixed price and a timeline against that scope."]},{"heading":"What you have at the end","body":["A document that makes the project fundable and buildable, and is yours whatever you do next.",["A defined scope, prioritised, with what is out of scope written down as plainly as what is in.","A fixed price and timeline for building it.","The reasoning, so a decision can be revisited on purpose rather than by accident."],"You are free to take that document elsewhere. It happens, and the work was still worth doing."]},{"heading":"Who this suits","body":["Anyone who has been quoted wildly different prices for what they thought was the same project: that spread is almost always a scope that has not been pinned down.","Also teams who know something needs building but cannot yet write down what \"done\" looks like."]},{"heading":"What you can bring to us","body":[["A startup idea that needs an MVP scope before you spend money on it.","A project that needs a written specification, so that quotes can be compared fairly.","An internal tool or digital product your company has discussed for a year.","An existing product where nobody agrees on what to build next."],"This is software product consulting from people who write the code, so the plan is checked against what building it really takes."]}],"process":{"heading":"The process, step by step","steps":[{"title":"Briefing","body":"What you want to achieve, for whom, your budget range and what you already know or have tried."},{"title":"User and market research","body":"Conversations with the people who will use it, and a look at what they use now, including competing products."},{"title":"MVP scope","body":"Features split into what launch needs, what can wait and what should be dropped, with the reasons written down."},{"title":"Technical plan","body":"How it would be built, the main risks, and flows or wireframes where words are not enough."},{"title":"Roadmap and fixed price","body":"A delivery plan, plus a fixed price to build it with us. The document is yours to take anywhere."}]},"diagram":{"heading":"From an idea to a buildable plan","caption":"What goes in, what gets decided, and what you hold at the end.","layers":[{"label":"What you bring","nodes":["The idea","Goals and budget","Your users","What exists today"]},{"label":"What we examine","nodes":["User needs","Competing products","Technical risks","The process around the software"]},{"label":"What gets decided","nodes":["MVP features","What waits","What is dropped","Technology choices"]},{"label":"What you receive","nodes":["Written specification","Wireframes","Product roadmap","Fixed price and timeline"]}]},"faq":[{"question":"What does product strategy include?","answer":"Research with your users, a prioritised MVP scope, a technical plan and a roadmap, ending in a written specification and a fixed price to build it."},{"question":"Why not go straight to development?","answer":"You can, if the scope is already clear. If you have been quoted very different prices for the same project, that usually means the scope is not pinned down, and this work is what fixes it."},{"question":"Am I obliged to build with you afterwards?","answer":"No. The specification is yours and any competent team can quote against it."},{"question":"How do you decide what goes into the MVP?","answer":"We ask what a customer would pay for or a team would rely on from day one. Anything that a real user can live without at launch waits, and that decision is written down with its reason."},{"question":"How long does the strategy phase take?","answer":"It is a short, concentrated engagement rather than a long consultancy. You get the exact length with the quote, because it depends on how much is already known."},{"question":"Can you review a specification we already have?","answer":"Yes. We read it, point out the gaps and risks, and quote against it if it holds up."}],"related":[{"label":"SaaS development","path":"/services/saas-development"},{"label":"Mobile app development","path":"/services/mobile-app-development"},{"label":"Custom software development","path":"/services/custom-software"}]}}]}