Skip to content

Web app development · operations softwareNot spreadsheets.
One system.

We bring quotes, orders and operations into one piece of software. First working version in 8-16 weeks, with progress shown in a working demo every week.

quotes_FINAL_v3 (2).xlsx
NoCustomerProductQtyAmountStatus
1038Kaya YapıSectional door274,000sent
1039Deniz MarketHigh-speed door148,500?
1040Anadolu DepoBarrier396,000pending OK
1041Mavi OtelAutomatic door261,200cancelled?
1042Sample LogisticsHigh-speed door4186,400approved??
1043Güney TekstilSectional door6212,000waiting
1044Kuzey MetalBarrier131,800
1045Ada LojistikHigh-speed door293,100revised
Inbox

RE: RE: Is the price on quote 1042 current?

sales@example-mfg.com · 3 replies

Can you resend the latest price for Sample Logistics, 4 units? The one in the sheet may be old.

Production group · messages

Has the Sample Logistics order gone into production?

Didn’t check the sheet, I think it was in an email.

Same record in four places · sample scenario

Process map

Process first.
Software second.

In the first week we draw the process map: who does what, in which order, and where the work gets stuck. The software is built to match this map one to one.

  1. SalesQuote prepared
  2. SalesCustomer approval
  3. ManagementOver the limit?
  4. ManagementManager approval
  5. ProductionWork order
  6. ShippingShip and invoice
Week 1 · process map · sample

One record

The same data,
entered once.

When a quote is approved, the order is created from the same record, and when the order is approved, so is the work order. No one types anything twice, and everyone sees the latest status on the same screen.

panel.example-mfg.com

Sample Mfg

  • Boards
  • Quotes
  • Orders
  • Production
  • Reports

Order flow

New quote

Quote

Approval

Production

Shipping

#1042

Sample Logistics

4 × High-speed door

Sample interface · fictional company

Roles and permissions

The same record,
only what you need.

Sales sees the amount, production sees the size, management approves. The role and permission structure, security and KVKK (Turkish data protection law) requirements are set up in the first version.

Sales

Quote #1042

Customer
Sample Logistics
Amount
186,400
Discount
4%
Unit cost
••••
Production note
Read only

Production

Quote #1042

Customer
Sample Logistics
Qty
4
Size
4200 × 4500 mm
Amount
••••
Discount
••••

Management

Can approve

Quote #1042

Customer
Sample Logistics
Amount
186,400
Unit cost
Visible
Profit margin
Visible
Approval
Authorized
Same record, three roles · sample scenario

Integration

Your existing tools
stay in place.

We integrate with accounting, e-commerce, CRM and calendar tools that have an API. For tools without one, we design import and export flows.

Sample Manufacturing

Operations software

  • Accounting

    API · invoice

  • E-commerce

    API · order

  • CRM

    API · customer

  • Calendar

    API · due date

  • Tool without an API

    Import / export

Measurement

Success means
faster work.

Success is measured by shorter quote times, a lower error rate and work running visibly through the system. The data comes from the system's own records.

09:12

Quote created

Sales

09:40

Manager approval

Management

10:05

Work order opened

Production

Next day 16:30

Shipped and invoiced

Shipping

Quote → approval

From the record's own timestamps

28 min

Re-entered data

The same record through the whole process

None

Work status

On one screen, for everyone

Live

Sample record · measures from the system’s own records

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

  1. 01Process mapping and MVP scope design
  2. 02User flows and interface design
  3. 03Development with modern web technologies
  4. 04Roles and permissions, security and KVKK (Turkish data protection law) structure
  5. 05Integration with your existing tools (API)
  6. 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.

Thin lines splitting into three paths from a single node on the left, the bright neon green path ending at an orange node, conceptual illustration
Conceptual illustration

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.

Software path by situation
Your situationUsually the right pathWhy
The process is a standard task everyone in your sector does (accounting, email, calendar)Off-the-shelf softwareSolving 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 connectedOff-the-shelf tools and automationIf 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 workCustom web appYou keep the rules, data and evolution of your core business under your own control
The idea has not been validated yetA narrow first version that solves the most expensive bottleneckValidate 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.

See the AI and automation page

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.

Four thin isometric layers stacked on top of each other with a single neon green line passing vertically through them, an orange node at the top, conceptual illustration
Conceptual illustration
  • 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

OWASP Top 10:2025 risk items and design review questions
Risk (OWASP Top 10:2025)What it meansQuestion asked in design
A01 Broken Access ControlA user can reach data or actions they have no permission forAre permission checks done on the server, is the role table written down?
A02 Security MisconfigurationDefault or wrong settings are left openHave environment settings been reviewed, are unneeded services turned off?
A03 Software Supply Chain FailuresVulnerabilities in the libraries and tools usedAre dependencies up to date and on supported versions?
A04 Cryptographic FailuresData stored or sent without encryptionAre connections encrypted, is sensitive data stored in a protected way?
A05 InjectionUser input being run like a commandIs input validated, are database queries written safely?
A06 Insecure DesignRisks not considered at the design stageWere permission and misuse scenarios discussed in design?
A07 Authentication FailuresWeak session and password managementAre sessions and passwords managed with secure methods?
A08 Software or Data Integrity FailuresUnverified updates or dataAre the source and integrity of the released version checked?
A09 Security Logging and Alerting FailuresEvents that are not logged or noticedAre critical actions written to the audit log, are events noticed?
A10 Mishandling of Exceptional ConditionsError states handled without controlAre 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.

Four milestones on a horizontal neon green line, the first three hollow green circles, the last an orange node, with thin rectangles growing above them, conceptual illustration
Conceptual illustration

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.

Phase 1 scope and what is left out on purpose
TopicIn Phase 1Left out on purposeWhy
FlowOne end-to-end flowSecondary and rare flowsValidation is faster, the error surface is smaller
PermissionsRole and permission structureDetailed custom permission rulesThe permission base is built first, fine-tuning comes later
LoggingAudit logPolished reporting screensLogging cannot be added later, reports can
DataCleaning and migrating existing dataThe entire old archiveUnused data slows the system down and causes confusion
IntegrationThe single most critical connectionSecondary integrationsEvery connection is a separate work item
MobileWeb interface, mobile friendlyStore appHandled 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

  1. 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.

  2. 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.

  3. 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.

  4. 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.

Items transferred at delivery
Delivery itemWhat it means
Source code repositoryAll of the app's code, with its history, in a repository you control
Infrastructure and account accessYou become the owner and administrator of the server, domain and service accounts
Environment settings and secret keysThe settings and keys the app needs to run are handed over securely
DocumentationSetup, maintenance and business rules are written down, so another team can take over
Data exportYou can export your data in a standard format
Written rights transferThe 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.

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 quote

What 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.

  1. Week 1

    Process map

    Who does what, in which order, and where the work gets stuck.

  2. Every week

    Working demo

    Progress is shown with working software, not slides.

  3. 8-16 weeks

    First working version

    The most expensive bottleneck is solved end to end.

  4. Go-live

    Training and handover

    Source code, documentation and setup information are handed over.

  5. 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.

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.

Other services in the Build layer