# Custom software and web application development

We build the web applications and admin panels your team uses every day, integrations that move data between the systems you already run, and automations that take over repetitive manual work. We start from your current workflow, not from software, and if an off-the-shelf product does the job we say so.

[Tell us what you need](https://rufystudio.com/en/contact?service=custom-software)

[All services](https://rufystudio.com/en/services)

Platform

React · TypeScript · PostgreSQL

Who it is for

## Who custom software is for, and who it is not for

A good fit

- **A process run on spreadsheets and WhatsApp groups**
  Orders live in a spreadsheet, approvals in a chat group, and nobody can tell who changed what and when. We move that process into an admin panel with roles, permissions and a change history.
- **Two systems that do not talk to each other**
  Enquiries from your website form retyped into the CRM, CRM records copied into quote files by hand. We write an integration that moves the data automatically through the systems’ APIs and tells you when something goes wrong.
- **Work that off-the-shelf software only partly covers**
  Writing the missing piece is often cheaper than replacing the software you use: a small panel connected to the existing system, a reporting screen or an approval step.
- **A signed-in area for customers or dealers**
  A web application where your customers or partners sign in with their own account to track orders, documents, quotes or applications. We build it to work on phones too; if a separate mobile app is needed, that goes through our mobile app development service.
- **Teams doing the same manual task every day**
  Preparing the same report every morning, copying incoming forms into a spreadsheet, emailing a customer when a status changes. We automate these with scheduled jobs and triggers, and log every run.

Not a fit

- **Jobs an established product already does well**
  Accounting, payroll, e-invoicing, general-purpose CRM and project tracking all have established products. Writing them from scratch costs more, and keeping up with regulation changes becomes your burden. For a request like that we recommend the product and, where needed, an integration to it.
- **ERP projects that replace all of a company’s processes at once**
  Projects that move production, stock, purchasing and finance onto a new system in one go are beyond the scale we take on. We can build the pieces that connect to such a system.
- **A process nobody owns**
  If it is unclear who will use the panel every day and who sets its rules, software will not fix the process; it will only record the confusion. We need to start with someone who knows the process and can make decisions.

Platform

## Off-the-shelf software, an integration or a custom build

The first decision is made before any code is written. The proposal says which of the three routes we recommend and why; sometimes the right answer is to write no code at all.

- **Off-the-shelf software (SaaS)**
  When
  When the need is common in your sector and your process fits the flow the software assumes. Setup is quick, and the provider handles updates and infrastructure security. Our part is then limited to helping you choose and, where needed, integrating it.
  The trade-off
  Ongoing per-user fees, dependence on the provider’s product decisions, and your data sitting on the provider’s servers.
- **Off-the-shelf software plus an integration**
  When
  When the systems you use each do their job well but do not talk to each other. Without replacing them, we write a layer that moves data between them through their APIs.
  The trade-off
  An integration depends on the APIs of the systems it connects. If a provider changes its API, the integration must be updated too.
- **Custom web application**
  React · TypeScript · PostgreSQL · Supabase
  When
  When the process is specific to your business, when different roles reach the same data with different permissions, or when per-user costs of off-the-shelf tools grow heavy as the team grows. We build the interface with React and TypeScript and store the data in PostgreSQL.
  The trade-off
  Maintenance, security updates and new needs are now your software’s job. Who takes that on is agreed in writing before handover.

Deliverables

## What you receive at the end of the project

### Analysis

5 items

1. Workflow map: who does what today, with which tools
2. Scope document: what is in the first release and what comes later
3. Data model: tables, fields and the relationships between them
4. Roles and permissions table: which user sees what and can change what
5. Integration map: which data flows from which system, in which direction, how often

### Development

6 items

1. The web application, on a staging URL and live
2. User sign-in, roles and permissions
3. Change history: who changed what, and when
4. Integrations, automations and failure alerts
5. Data migrated from existing spreadsheets
6. The complete source code, in a Git repository on your account

### Handover

4 items

1. Runbook: backups, what to do when something fails, routine operations
2. Technical documentation: architecture, environment settings, third-party services used
3. List of accounts, access and API keys
4. Training for the people who will use the panel

Process

## The process, step by step, and what each step produces

1. **Process analysis**
   We map today’s workflow together with the people who run it every day: which spreadsheet, which message, which approval. This is where we decide whether off-the-shelf software would do the job.
   Output
   Workflow map and a written recommendation: off-the-shelf, integration or custom build
2. **Scope and data model**
   We write down the screens, roles, data model and integrations for the first release. We plan a large system not in one go but as parts that are each useful on their own.
   Output
   Scope document, data model, roles and permissions table
3. **Prototype**
   We try a clickable prototype of the main screens with the people who will use the panel. The screens are shaped around the information users look at in their spreadsheets today.
   Output
   Clickable prototype
4. **Development**
   We build the application part by part on a staging URL. As each part is finished, you try it yourself with a copy of your data.
   Output
   Working versions on a staging URL
5. **Data migration and switchover**
   We clean the data in your existing spreadsheets and move it into the new system. For a short period the old method and the new system run side by side and we compare the results; the old method is dropped once the comparison holds up.
   Output
   Migrated data, a list of records that could not be migrated, and a switchover plan
6. **Handover**
   We train the people who will use the panel and hand over the source code, access, technical documentation and runbook.
   Output
   Handover pack: runbook, technical documentation, source code and access list

Risks

## Common problems in custom software projects and how we prevent them

- **Integrations that fail without anyone noticing**
  An integration that silently stops when the other system does not respond for a few minutes, or when unexpected data arrives, means a missing order gets noticed days later. In every integration we retry failed requests, and if they still fail, we alert the person you choose.
- **Automations nobody can see into**
  If you cannot see when an automation ran, what it changed and whether it failed, there is no way to tell what went wrong when a problem appears. We log every run with its time, result and error message.
- **Permissions wider than needed**
  A panel where everyone can see and change everything turns a single wrong click, or a departing employee, into a risk. We put the roles and permissions table up for your approval before design, and enforce the rules at the database level, not only on screen.
- **Scope growing at every meeting**
  Once the panel is in use, new requests arrive; that is a good sign, but it should not delay the first release. We write down out-of-scope requests with their impact and, as you decide, add them to the first release or to the list that follows it.
- **Messy data in old spreadsheets**
  The same customer spelled several different ways, text in date fields. We clean the data before migrating it and show you a list of the records that could not be migrated.
- **A system only its author can touch**
  An undocumented internal tool becomes a black box when the person who wrote it leaves. We keep the code in your repository and update the technical documentation and runbook throughout the project.

Example

## A live example: Santra’s access rules

- **[Santra](https://rufystudio.com/en/work/santra)**
  Not a panel or integration project, but the backend of Santra, a mobile game we built.There too, which user can read and write which data is defined at the database level, with row-level security (RLS) rules.
  Mobile app
  [App Store](https://apps.apple.com/us/app/santra-2-club-1-player/id6802406040) [Google Play](https://play.google.com/store/apps/details?id=com.rufy.santra)

Cost

## What determines the cost of custom software

- **Number of roles and screens**: How many types of user there are, and whether each needs its own screens. A few roles seeing the same list with different permissions are less work than panels that are each designed separately.
- **Integrations and the state of the other system**: Connecting to a documented API is far less work than connecting to a system with no API or patchy documentation. Before the proposal we review the API documentation of the systems to be connected.
- **Complexity of the business rules**: Approval chains, exceptions, calculations that change with circumstances. How much time the person who knows the rules can give the project also affects duration and cost.
- **Data migration**: How many existing spreadsheets there are and how messy they are. Data that needs cleaning makes migration a work item in its own right.
- **Reporting**: There is a large difference in work between a few fixed reports and a reporting screen where users build their own filters.
- **Costs that continue after launch**: Server and database hosting, email or SMS delivery services, API fees of the off-the-shelf tools you connect to, and maintenance. We list these separately in the proposal.

Once the scope is agreed in writing, we prepare an itemised proposal. Which post-launch support tasks are covered, and for how long, is stated separately in the proposal.

[Request a proposal](https://rufystudio.com/en/contact?service=custom-software)

Ownership & handover

## Who keeps the source code, database and data

When the project ends, the software and the data in it are under your control.

Handover list

- **Source code**: The full code sits in your account with its Git repository. There is no licence or lock that stops you continuing with another developer.
- **Server, database and data**: Hosting and database accounts are opened in your company’s name and billed to you. You can take a full export of your data whenever you want.
- **Where the data is held**: We choose the server region together at the start of the project. If personal data is processed, we give you in writing the technical information needed for a KVKK (Turkish data protection law) assessment: which data, with which provider, in which country.
- **API keys and service accounts**: The API keys used in integrations are generated in your accounts. The handover list states where each key is used and how to rotate it.

FAQ

## Questions people ask before commissioning custom software

[Ask your question](https://rufystudio.com/en/contact?service=custom-software)

### Should I use off-the-shelf software or commission custom software?

If your need is common in your sector and your process fits an existing product’s flow, off-the-shelf software is cheaper and faster. Custom software or an integration starts to make sense when the process is specific to your business, when data is moved by hand between the systems you use, or when per-user costs of ready-made products grow heavy. After the process analysis we give you a written recommendation with reasons; if a ready-made product is enough, we say so.

### What determines the cost of custom software?

Mostly the number of roles and screens, and the state of the APIs of the systems to be connected. The other factors are listed in the cost section on this page; once the scope is agreed in writing we give an itemised proposal.

### Do you work at a fixed price or by the hour?

We give a fixed-price proposal for a first release whose scope is agreed in writing. For requests outside that scope and development after launch, we either prepare a separate proposal or work at an hourly rate agreed in advance. Which applies is written in the contract.

### Will the software integrate with my existing systems?

If the system has a documented API, usually yes. Without an API there are other routes, such as file exchange (CSV or Excel), direct database access or reading data that arrives by email; we say up front that these are more fragile. Before the proposal we review the documentation of the systems to be connected and write down what happens on failure for each integration.

### Where is the data stored, and what does KVKK require?

The data is held in a server region we choose together at the start of the project. If personal data is processed, a server located outside Turkey is a matter that needs a separate assessment under KVKK, the Turkish data protection law. Your legal adviser makes the legal assessment; we provide the technical information it needs in writing: which data, with which provider, in which country, accessible by whom.

### Who owns the source code and the data?

You do. The complete code sits in a Git repository on your account, and the data in a database opened in your name. The technical documentation and runbook are written so that you can continue the software with another developer.

### Do you provide support after launch?

Yes. After launch, for the period written in the proposal, we monitor the logs of the integrations and automations and fix the bugs that come up. Later maintenance, updates and new features are written into the proposal as separate items.

### Can we start with a small piece of work?

Yes, and we often recommend it: a panel that takes over a single process, or a single integration between two systems. The first piece shows both whether the software works for you and how we work together. Later parts are added on top of the same data model.

### Do you also build mobile apps?

Yes, as a separate service. iOS and Android apps, store release and developer accounts are covered on our mobile app development page. The backend and admin panel behind a mobile app, on the other hand, are part of the work on this page.

Related services

## Often considered alongside this service

- **[Mobile app development](https://rufystudio.com/en/services/mobile-app-development)**
  iOS and Android apps. Depending on the project we use Kotlin Multiplatform or React Native, so the part both platforms share is written once. Santra and Aera Wallet, which we built and released, are on the App Store and Google Play.
  Kotlin Multiplatform · React Native · iOS · Android
- **[Web design & development](https://rufystudio.com/en/services/web-design-development)**
  Company websites, service and product pages, bilingual sites. We build either a custom-coded site or WordPress with a custom theme, whichever fits; when we replace an existing site, old URLs are 301-redirected to the new pages and the switch is monitored in Search Console.
  React · TypeScript · Tailwind CSS · WordPress
- **[E-commerce website](https://rufystudio.com/en/services/e-commerce-website)**
  Sites that sell products. We choose the platform to fit the job: WooCommerce, Shopify, a Turkish platform such as ikas, or a custom-coded store. On the payment side we set up iyzico, PayTR or your bank’s virtual POS with instalments; on the shipping side, shipment creation and tracking.
  WooCommerce · Shopify · iyzico · PayTR

Rufy Studio

## Tell us which workflow you want turned into software

Write how you do this work today, which tools you use and where it gets stuck; our first conversation starts from that workflow.

[Tell us what you need](https://rufystudio.com/en/contact?service=custom-software)

---
Source: https://rufystudio.com/en/services/custom-software-development
