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.
Platform
React · TypeScript · PostgreSQL
01Who it is for
A good fit
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.
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.
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 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.
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
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.
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.
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.
02Platform
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.
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.
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.
03Deliverables
04Process
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
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
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
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
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
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
05Risks
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.
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.
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.
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.
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.
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.
06Example
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
07Cost
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.
08Ownership & handover
Handover list
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.
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.
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.
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.
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.
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.
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.
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.
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.
Rufy Studio
Write how you do this work today, which tools you use and where it gets stuck; our first conversation starts from that workflow.