Short answer
Web app development means bringing a business process that runs on spreadsheets, emails and disconnected tools into one piece of software. USFORM takes an MVP approach: the most critical flow goes live first, in 8-16 weeks, and the app then grows based on data.
Scope
What is in a web app project?
What you get
- 01Process mapping and MVP scope design
- 02User flows and interface design
- 03Development with modern web technologies
- 04Roles and permissions, security and KVKK (Turkish data protection law) structure
- 05Integration with your existing tools (API)
- 06Go-live, training and iteration plan
Who it is for
- Businesses that run operations on Excel and email
- Companies whose processes off-the-shelf packages do not fit
- Teams that want to digitize their quote, order, production or appointment flow
- Teams that want software for their own staff, not a product to sell
Problems it solves
- The same data is typed into several spreadsheets by hand
- The process depends on people, and work stops when someone is away
- Off-the-shelf software covers only half the process
- Management cannot see where the work stands right now
Last updated: September 29, 2026
Decision
Off-the-shelf software, Excel and automation, or a custom app: which one?
Not every problem needs new software. The right question is which tool fits your process and which one will lock you in later.

You have three paths: buy off-the-shelf software, connect your existing tools with automation, or have a web app built for your process. Software engineering writing repeats one principle for this decision: solve the functions that do not set you apart with a package, configure the package rather than customizing it heavily, and keep your own core business under your own control.
The table below applies this principle to four typical situations. Sources are listed at the end of the page.
| Your situation | Usually the right path | Why |
|---|---|---|
| The process is a standard task everyone in your sector does (accounting, email, calendar) | Off-the-shelf software | Solving a function that does not differentiate you with a package makes sense. Heavy customization makes maintenance harder |
| The problem is that several tools are not connected | Off-the-shelf tools and automation | If data flows from one tool to the next on its own, you may not need new software |
| The process makes a difference in competition, or packages cover only half the work | Custom web app | You keep the rules, data and evolution of your core business under your own control |
| The idea has not been validated yet | A narrow first version that solves the most expensive bottleneck | Validate first, then grow with data. A first version that does everything delays validation |
Sources: Martin Fowler, Joel Spolsky and the GOV.UK technology guidance. These are opinion pieces, not measured data.
Signs that you have reached the limit of Excel
- Several people enter the same data in several places.
- There is debate about which file version is correct.
- Who can see and change what needs separate permissions.
- Files with personal data are passed around by email and messaging apps.
- You have to ask someone to find out where the work stands.
- The process stops when one person is on leave.
If an off-the-shelf tool is enough, we say so
In discovery, we first check whether your existing tools can solve the problem. If off-the-shelf software and automation meet your need, we write that openly. A custom app only makes sense when those two paths are not enough, or when the process itself is what sets you apart.
Architecture
What is built behind the screens?
The value of a web app is not in its screens but in the structure behind them. If permissions, data and logging are not set up right from the start, adding them later is expensive.

Roles and permissions
Who sees, edits, approves and deletes what? These questions are written into a permission table from the start. The table shapes both the screens and the rules on the server.
Data model
Linked tables replace Excel columns. Customer, order and work order are parts of the same record. This structure is the single source of truth.
Integration
Connections are built with email, accounting, CRM and calendar tools. The scope states which comes in the first phase and which comes later. For tools without an API, an import and export flow is designed.
Audit log
The answer to who changed what, and when, stays in the system. When there is a wrong record or a dispute, you can look back.
Backup and recovery
Taking a backup is not enough, restoring it is tested too. Backup frequency and recovery steps are documented at delivery.
Infrastructure and access
Server location, account ownership and environment settings are clarified at the start of the project. The software is kept on versions the vendor supports, and no outdated components are left behind.
The technology choice (language, database, hosting) is made during discovery, after your needs and your team's maintenance capacity are written down. We do not give version numbers here, because versions date. The principle that does not change is to stay on versions the vendor supports and keep the stack standard. This also reduces dependence on the agency.
Security
Security and KVKK: which questions are asked in the design review?
Security is not a layer stuck on later, it is the sum of design decisions. This section is not a certificate or a compliance statement. It is the list of questions asked in the design review. Which items are in your project's scope is written in the quote.
OWASP Top 10:2025 items and the questions asked in design
| Risk (OWASP Top 10:2025) | What it means | Question asked in design |
|---|---|---|
| A01 Broken Access Control | A user can reach data or actions they have no permission for | Are permission checks done on the server, is the role table written down? |
| A02 Security Misconfiguration | Default or wrong settings are left open | Have environment settings been reviewed, are unneeded services turned off? |
| A03 Software Supply Chain Failures | Vulnerabilities in the libraries and tools used | Are dependencies up to date and on supported versions? |
| A04 Cryptographic Failures | Data stored or sent without encryption | Are connections encrypted, is sensitive data stored in a protected way? |
| A05 Injection | User input being run like a command | Is input validated, are database queries written safely? |
| A06 Insecure Design | Risks not considered at the design stage | Were permission and misuse scenarios discussed in design? |
| A07 Authentication Failures | Weak session and password management | Are sessions and passwords managed with secure methods? |
| A08 Software or Data Integrity Failures | Unverified updates or data | Are the source and integrity of the released version checked? |
| A09 Security Logging and Alerting Failures | Events that are not logged or noticed | Are critical actions written to the audit log, are events noticed? |
| A10 Mishandling of Exceptional Conditions | Error states handled without control | Are errors handled without leaking internal information? |
This table is not a certificate or a compliance statement. It is a checklist. Which items are in scope is written in the quote. Source: OWASP Top 10:2025.
KVKK: what should the system make possible?
KVKK is the Turkish Personal Data Protection Law. The Turkish Personal Data Protection Authority's Personal Data Security Guide (technical and organizational measures) lists topics such as a permission matrix and permission control, access and log records, backups, encryption, penetration testing and application security. A well-designed web app makes most of these measures technically possible. Running these measures is part of your own process.
It is good practice to write the data controller and data processor roles into the contract from the start. The provisions of Law No. 6698 on transfers abroad changed on June 1, 2024. If the server or cloud service is outside Turkey, the transfer needs a legal basis. The Authority's guide lists these as an adequacy decision, appropriate safeguards such as standard contracts, and incidental transfers. The standard contract route also requires notifying the Authority. That is why we clarify the server location at the start of the project and put it to your legal advisor for review.
This section is not legal advice. For your obligations and penalties, refer to the Authority's current texts and a legal advisor. We do not give article numbers or penalty amounts here, because they change.
Accessibility
For screens built for internal users, we recommend WCAG 2.2 level AA as a quality goal. W3C published this version as a Recommendation on December 12, 2024. Its new criteria at level AA are: a focused element is not hidden by another element (2.4.11), an alternative to dragging movements (2.5.7), touch targets of sufficient size (2.5.8) and accessible authentication (3.3.8). Your legal obligations may vary by sector, so please consult your legal advisor on this.
Scope
What goes into Phase 1, and what is left out on purpose?
The success of the first version depends less on what it does than on what it deliberately does not do.

The most expensive bottleneck method
The whole process does not move into software at once. First, the most expensive step in the process is found. The measures are time lost, the cost of errors and the damage delays do to the business. The first version solves only this bottleneck, end to end. Later phases are planned from the first version's usage data.
| Topic | In Phase 1 | Left out on purpose | Why |
|---|---|---|---|
| Flow | One end-to-end flow | Secondary and rare flows | Validation is faster, the error surface is smaller |
| Permissions | Role and permission structure | Detailed custom permission rules | The permission base is built first, fine-tuning comes later |
| Logging | Audit log | Polished reporting screens | Logging cannot be added later, reports can |
| Data | Cleaning and migrating existing data | The entire old archive | Unused data slows the system down and causes confusion |
| Integration | The single most critical connection | Secondary integrations | Every connection is a separate work item |
| Mobile | Web interface, mobile friendly | Store app | Handled as a separate project once data proves the need |
Acceptance criteria
Written acceptance criteria for when the first version counts as "working" are set from the start. A criterion should be measurable, such as a user being able to complete the one main flow from start to finish. Without criteria the project can never be called done, and it drags on forever.
Sample phase plan
- 01
Phase 0: Discovery and scope
In the first week the process map is drawn, and the data inventory and risks are written down. You are expected to set aside working time with the people who know the process.
DeliverableProcess map, phase plan and itemized budget.
- 02
Phase 1: First working version
The most expensive bottleneck is solved end to end. A working demo is shown every week. The typical duration is 8 to 16 weeks.
DeliverableReleased version, training, source code and documentation.
- 03
Phase 2: Integration and reporting
Secondary integrations and reports are added based on the first version's usage data.
DeliverableAdditional modules delivered with written scope and cost.
- 04
Phase 3: Scaling and improvement
Performance and new needs are handled as the number of users and the data grow.
DeliverableMonthly development cycle or maintenance with an SLA.
Examples
Three sample scenarios
All three scenarios are fictional. They do not describe a client, they show how the first phase is chosen.
- Example scenario · fictional
Quote and order tracking
- Situation
- A manufacturer prepares quotes in Excel and takes orders by email. The sales manager is the only person who knows which quote is at which stage.
- Approach
- Quote preparation and tracking is chosen as the most expensive bottleneck. Phase 1 builds the flow for creating, approving and converting a quote into an order, plus the role structure.
- Outcome
- Quotes sit in one place and their status is visible. Stock and accounting integration is left to the second phase.
- Example scenario · fictional
Dealer portal
- Situation
- Dealers ask for orders, price lists and documents over WhatsApp and email. When the price list is updated, old files keep circulating.
- Approach
- Phase 1 builds a dealer login, the current price list and order creation. On the management side, orders and dealer records come together in one panel.
- Outcome
- Dealers always see the current price. Account balance and the ERP connection are planned once the first phase is seen working.
- Example scenario · fictional
Customer request and service management
- Situation
- Service requests arrive by phone, email and forms. Who owns a request and where it stands lives in people's memory.
- Approach
- In Phase 1, requests from all channels are collected in one record pool, an owner is assigned and status is tracked. The audit log is on from the start.
- Outcome
- The owner and history of every request stay in the system. Customer notifications and reports wait for the next phase.
Ownership
Code and ownership: what passes to you at delivery?
"You own the source code" is not a guarantee on its own. What is transferred, with which document and when, must be in writing.
| Delivery item | What it means |
|---|---|
| Source code repository | All of the app's code, with its history, in a repository you control |
| Infrastructure and account access | You become the owner and administrator of the server, domain and service accounts |
| Environment settings and secret keys | The settings and keys the app needs to run are handed over securely |
| Documentation | Setup, maintenance and business rules are written down, so another team can take over |
| Data export | You can export your data in a standard format |
| Written rights transfer | The transfer of rights in the software to you is stated clearly in the contract |
A point that comes up often in legal writing: if the contract does not say so, the developer may have no obligation to hand over the source code. Under Turkey's Law No. 5846 on Intellectual and Artistic Works, economic rights are transferred in writing, and the transferred rights are listed one by one. That is why we recommend writing the transfer into the contract from the start.
This section is not legal advice. Have a lawyer read your contract. Our default approach: code, documentation and setup information are handed over, and the transfer of economic rights is written into the contract with each transferred right listed, subject to full payment. Open source and third-party components are subject to their own licenses, and the list is given at delivery.
What happens after delivery?
A 30-day stabilization period after delivery is standard. During this period, bugs that show up in live use are fixed. After that, we offer a monthly development cycle or maintenance with an SLA.
If you part ways with the agency, the documentation, the standard stack and the transferred accounts let another team take over. Maintenance cost is also itemized at the quote stage, because the real cost of custom software is often in maintenance.
Confidentiality
A non-disclosure agreement (NDA) is signed before work starts. Client information is not kept in personal accounts or uncontrolled tools.
Risks
Six common mistakes
Most of the mistakes below come from decisions made before a single line of code is written.
Fitting everything into Phase 1
The longer the list, the later the first version. Software that never gets used validates nothing.
Heavily customizing an off-the-shelf product
The more you customize, the harder maintenance gets. Configuring an off-the-shelf product is more sustainable than heavily changing its code.
Ignoring maintenance cost
The lifetime cost of custom software is not only the development fee. If the quote has no maintenance line, ask about it.
Not writing down source code and rights
If the transfer is not in the contract, you may have to rewrite the software when you change agencies.
Leaving data migration to the end
Uncleaned old data damages trust in the new system from day one. Data migration is part of the first phase.
Comparing quotes on price alone
A fixed-price quote and a time-and-materials quote do not measure the same thing. Ask about out-of-scope items and how change requests are handled.
Preparation
What to prepare before asking for a quote
This list helps quotes come back accurate and comparable. Even one-sentence answers are enough.
- Which files and channels do you use today: Excel files, email, messaging groups?
- What are the steps of the process, and who owns each step?
- Which step costs the most time or money?
- Which personal data is processed, and who should see it?
- Which existing tools does the new system need to talk to?
- Who is the decision maker, and who will accept the first version?
- What is the quality of your data today: are there duplicates or missing records?
- What is your budget range and how much time pressure do you have?
- Which clauses do you want in the contract: rights transfer, source code, documentation, maintenance.
Glossary
Short glossary
- Web app
- Software that runs in the browser, takes data from users, runs business rules and keeps records. It has login, roles and a database. A website gives information, a web app does work.
- Role and permission matrix
- A table showing which role can see which data and perform which action.
- Audit log
- A record that answers who changed which record, and when.
- API
- An interface that lets two pieces of software exchange data.
- Integration
- Connecting the new app to existing tools such as accounting, CRM or email.
- Phase 1
- The first working version, which solves the most expensive bottleneck end to end.
- Acceptance criteria
- Measurable conditions, written from the start, for the first version to count as working.
- Stabilization
- The period after delivery when bugs found in live use are fixed.
- Vendor lock-in
- A situation where the software can only be maintained by the company that built it.
- Data export
- Being able to take the data out of the system in a standard format.
Limits
What we don't promise
- We do not issue a security certificate or a KVKK compliance statement. We write the questions asked in the design review and the items included in the quote's scope, and we do not promise absolute security.
- We do not give legal advice. For KVKK, contracts and rights transfer, consult your legal advisor.
- Duration and cost become clear at the end of discovery. Nothing on this page is a binding quote.
- We do not promise automatic integration with tools that have no API. For those tools we design an import and export flow.
- Projects with heavy hardware integration or regulatory requirements need extra stages and are assessed separately.
Proof
Systems that work.
Our web apps that are live or in pilot. We state their stage as it is.
Vertical SaaS · Parking operationsPilot findingParkMetria
A vertical operating system that brings parking operations into one dashboard.
View the case record
Content operationsInternal tool · pilotContentOS
A content workflow that runs from the shoot to multi-channel content production.
View the case record
Health · PsychologyLive productDijital İlişki Dinamikleri
Turning a scientific scale into a safe digital self-assessment tool.
View the case record
Quote
Priced by scope, in phases.
There is no fixed package price. After discovery the scope is split into phases, and the cost and deliverables of each phase are given in writing. Send the form and we will write the first phase and its quote.
Request a quoteWhat shapes the quote
- The flow the first version needs to solve
- User roles, permissions, security and KVKK structure
- Integrations with your existing tools
- The state and amount of the data to migrate
- Training, go-live and the maintenance model
A non-disclosure agreement (NDA) is signed before work starts. No vendor lock-in is created.
Process
How it works
First working version in 8-16 weeks. Process map in the first week, a working demo every week.
Week 1
Process map
Who does what, in which order, and where the work gets stuck.
Every week
Working demo
Progress is shown with working software, not slides.
8-16 weeks
First working version
The most expensive bottleneck is solved end to end.
Go-live
Training and handover
Source code, documentation and setup information are handed over.
After
Stabilization
30 days of stabilization, then monthly development or maintenance.
Assessment request
Web App Pre-Analysis
Send the short form and we will get back to you within one business day with our first findings on your process and the scope of the first version.
- 2-minute form
- Reply within 1 business day
- No sales pressure
Prefer to talk instead? Call +90 532 450 75 14.
Frequently asked questions
Web app development: frequently asked questions
We pick the most expensive bottleneck in the process, and the first version solves only that, end to end. We do not aim for a first version that does everything, because validation gets delayed and costs grow.
It is transferred to you in writing in the contract. Code, design files, documentation and setup information are handed over. The transfer of economic rights is written with each transferred right listed one by one, subject to full payment. Open source and third-party components come with their own licenses, and the list is given at delivery. This is not legal advice. We recommend having a lawyer read your contract.
We build integrations with accounting, e-commerce, CRM and calendar tools that have an API. For tools without an API, we design import and export flows.
A 30-day stabilization period is standard. After that, we offer a monthly development cycle or maintenance with an SLA.
A non-disclosure agreement (NDA) is signed before work starts. Client information is not kept in personal accounts or uncontrolled tools.
A website gives information. A web app takes data from users, runs business rules and keeps records. That is why it has login, roles and permissions, and a database.
If several people enter the same data, if there is debate about which file is correct, if visibility needs to depend on permissions, or if files with personal data are being passed around, you have reached the limit of Excel.
Off-the-shelf software makes sense for a standard task, automation makes sense when the problem is connecting tools, and a custom app makes sense when the process sets you apart from competitors or when packages cover only half the work. If an off-the-shelf tool is enough, we say so openly during discovery.
In the design review we use the OWASP Top 10:2025 items as a checklist: access control, input validation, authentication, audit logging and up-to-date dependencies, for example. Which items are in your project's scope is written in the quote. This is not a certificate or a compliance statement, and it is not a promise of absolute security.
We make technical measures such as a role and permission table, access logs and backups possible in the system. Running these measures and meeting your obligations as data controller are part of your own process. The contract states the data controller and data processor roles and the server location from the start. If the server or cloud service is outside Turkey, the transfer needs its own legal basis. This is not legal advice. Please consult your legal advisor.
One end-to-end flow that solves the most expensive bottleneck, the role and permission structure, the audit log and the migration of existing data. Secondary integrations, detailed reports and a mobile app are left to later phases.
A web app is built for one business's own process and used by that business's team. SaaS means selling the same software to many customers by subscription, so it needs a multi-tenant architecture, subscriptions and billing. If your goal is a system that works for your own team, you need a web app. If you want to sell a product, see the SaaS development page.
Custom software is a broader term that covers any system written for a specific business. We build software that runs in the browser. If you want a business app from scratch, this page is the right one. If the work is mostly about moving off an existing system, data migration and integration, the custom software development page fits better.
Sources
The official information on this page is based on the sources below. Fees and rules can change, so check the source before you decide.
- OWASP Top 10:2025Risk items. Accessed: September 29, 2026
- KVKK: Personal Data Security Guide (technical and organizational measures)In Turkish. Accessed: September 29, 2026
- KVKK: Guide on Transferring Personal Data AbroadAuthority page, in Turkish. Read the full text with your legal advisor
- W3C: Web Content Accessibility Guidelines (WCAG) 2.2Accessed: September 29, 2026
- W3C: What's New in WCAG 2.2New criteria at level AA. Accessed: September 29, 2026
- Martin Fowler: Utility vs Strategic DichotomyOpinion piece. Accessed: September 29, 2026
- Joel Spolsky: In Defense of Not-Invented-Here SyndromeOpinion piece. Accessed: September 29, 2026
- GOV.UK Technology Blog: To build or to buy, that is the technology questionAccessed: September 29, 2026
- GOV.UK Service Manual: Choosing technologyAccessed: September 29, 2026