Custom Software Development

We develop custom software for companies whose operations run through Excel, email, phone calls and disconnected systems: one ERP-connected web app your teams use every day.

Who it is for

Custom software development means designing and building an application around your workflows and existing systems. User roles, approval rules, reports and integrations together define the enterprise software scope. If an off-the-shelf product is sufficient, we consider it first.

When is it needed?

  • Operations: the plan is in Excel, changes come by phone, and no one can see the current status.
  • Finance: approvals wait in email, and it is unclear which stage a payment has reached.
  • Sales: quotes are stored in files; accepted orders are manually re-entered into the ERP.
  • Management: monthly reports are assembled manually, and figures are outdated by the meeting.
Moving from Excel to an operations platform

When is it unnecessary?

  • Off-the-shelf products are usually sufficient for standard processes such as accounting, payroll, e-Invoicing and basic CRM. For CRM: off-the-shelf or custom CRM?
  • When a ready-made product meets most needs and your team can adapt to it.
  • If the gap is small, keeping the existing product and building only the missing module is more economical.
Off-the-shelf or custom software?

Scope

We agree the scope during discovery. The example below is a typical first release bringing one operational process into a single web app.

  1. Role-based web panel

    Planning, approval and monitoring screens, accessible on phones too.

  2. Workflows and approvals

    Approval thresholds, sequence and exception rules.

  3. Integrations

    ERP, CRM and e-document connections, with an error queue.

  4. Notifications

    Delay and approval alerts by email, SMS and in-app notifications.

  5. Reports and dashboards

    Current status and bottlenecks; export to Excel.

  6. Access and security

    Roles, single sign-on (SSO), audit trails and backups.

Outside this example's scope

  • Replacing or reinstalling the ERP
  • Native iOS and Android apps (a later stage if needed)
  • Licence, SMS and cloud fees (charged directly to your accounts)

Assumptions

  • The ERP has an API or regular export capability and a test environment.
  • The process owner attends weekly demos and makes decisions.
  • The first release covers one process end to end, such as order to dispatch.
  • Only open records and master data are migrated.

How to keep the first release small: How do you define MVP scope?

Example scenarios

Explore the use cases

Each scenario starts with a role's working day; we define yours together during discovery.

  1. Dispatch planning

    Role
    Operations planner
    Input
    Open ERP orders, vehicle and warehouse capacity
    Action
    Orders are planned on one screen; at-risk trips are highlighted and changes are sent to drivers.
    Output
    Daily plan, driver task list and arrival notification for the recipient
  2. Payment approval

    Role
    Finance manager
    Input
    Supplier invoices, bank balances and budget items
    Action
    The approval sequence depends on amount and cost centre; approval can be given by phone.
    Output
    Approved payment list, bank instruction file and audit trail
  3. Quotes and orders

    Role
    Sales representative
    Input
    Price list, customer discount terms and stock information
    Action
    A quote is prepared from a template; quotes exceeding the discount limit go to a manager for approval.
    Output
    PDF quote; an order transferred to the ERP on acceptance

Integrations

Integration details

Custom software fills the gaps between your existing systems rather than replacing them. We document each flow's direction, frequency and error behaviour during discovery.

Systems that can be connected and typical data flows
SystemExamplesTransferred dataDirection and frequency
ERP and accountingLogo, Netsis, Mikro, SAPAccounts, products, prices, stock, orders and invoicesMaster data from the ERP at defined intervals; orders sent to the ERP immediately
CRMSalesforce, HubSpot, Dynamics 365Customers, opportunities and quotesBidirectional, when records change
Electronic documentsAuthorised e-document integrator APIe-Invoice, e-Archive, e-Delivery NoteSent to the integrator when a document is created
BankBank APIs and account statementsBalances, transactions and payment instructionsTransactions during the day; instructions after approval
FileExcel, CSV, SFTPPrice lists and bulk recordsScheduled imports and exports if no API is available

If the connection drops

The transfer queue, duplicate detection using job IDs and bounded retries are designed together. Temporary failures are retried at increasing intervals; jobs reaching an attempt or time limit are assigned to the responsible person. A reconciliation report compares both systems.

Details: How do you plan an ERP integration?

Product names are examples and do not imply a partnership.

Process

Steps in our process
  1. 01

    Discovery

    We observe the process on site, interview users and inventory systems and data.

    1–2 weeks
  2. 02

    Definition & Prototype

    The prototype is tested with real users in week 3; the first-release scope is documented.

    2–3 weeks
  3. 03

    Build

    Weekly working-software demos, automated tests and frequent releases.

    Two-week sprints,
    first release target: weeks 6–12
  4. 04

    Grow & Operate

    We measure usage and add modules; larger programmes proceed in stages.

    Ongoing

This is an illustrative schedule assessed once access and pilot scope are clear; the final duration is determined during discovery. Step-by-step details: how we work

Budget and timeline

We do not publish a price list; scope determines cost and duration. At the end of the discovery sprint, you receive a proposal with the scope and fee in writing.

Roles and rules
User roles, approval steps and exceptions.
Integrations
Number of systems and API availability.
Data migration
Which data, how many years of history, and how much cleaning it needs.
Platforms
Web, iOS, Android and offline use.
Security and compliance
KVKK, audit trails and SSO; the country where data is stored.
After launch
Support hours, monitoring and maintenance.
What determines the cost of custom software?
Discovery sprint
2 weeks Fixed scope, fixed fee
First release
6–12 weeks A first release scoped together, rather than the entire project
Larger programmes
In stages A 6–12 week target for the first stage

Delivery terms

Delivery and maintenance details

You remain independent of us: code, accounts and knowledge are yours from day one.

  1. Code and intellectual property

    Transfer of project-specific code and designs, third-party licences and usage rights are defined separately in the contract.

  2. Accounts

    Repository, domain, cloud and app-store accounts are registered to you from the outset.

  3. Documentation

    Architecture, setup and API notes are kept in the repository and updated with every release.

  4. Tests

    Automated tests cover critical flows; a release that fails testing does not go live.

  5. Handover

    Code is handed over to your team or a team you choose through joint sessions.

  6. Maintenance and support

    Maintenance scope, support hours, response targets and fees are defined in the proposal and contract.

How do we know the first release is complete?

Example scenario: In a purchase approval panel, an employee submits a request, an authorised manager approves it, and accounting exports the approved record. For the first release, we define acceptance criteria for the outcome of this flow, beyond the screens alone.

  • Business rules: requests above the approval threshold reach the correct person; unauthorised users cannot read or change another department's records.
  • Data: amounts and record relationships in a sample transfer are compared with the source; responsibility for incorrect and missing records is assigned.
  • Delivery: the accepted version, test results, setup steps and outstanding work are recorded together. A new approval rule is treated separately from a defect in an existing rule.

Mandatory tests and the person authorised to accept delivery on the business side are determined by the project scope. Eight technical checks for proposal discussions help you compare these decisions.

Frequently asked questions

What should we prepare for the first meeting?

A brief account of today's workflow, the tools you use and the step that wastes the most time is enough. If you can include the roles performing and approving work, the systems to connect and one example that must work in the first release, we can assess the scope more easily.

You do not need to prepare a technical specification; we identify unknowns together. Do not share passwords, access keys or real customer records in the form; remove personal and confidential information from examples. You can start with the sample requirements checklist.

Do we need a web app or a mobile app?

A web app is often sufficient for office-based teams and also opens in a phone browser. If field teams need a camera, barcode scanning, location or offline operation, we recommend a separate mobile app; both interfaces use the same backend. Details: enterprise mobile application development.

What should we look for when choosing a custom software company?

Compare proposals against the same workflow and acceptance criteria. Are data migration, integration errors, code and account ownership, and maintenance responsibilities clear? Also ask whether the work shown is a customer project or a product concept. The guide to choosing a software company includes a requirements checklist and questions to bring to a meeting.

What happens if the scope changes during the project?

We assess a new request's impact together at the weekly demo: either an equivalent piece of work is removed from the first release or the request is scheduled for a later release. Every decision affecting scope or fees is recorded in writing.

How much time will our team need to contribute?

During discovery, a few sessions for user interviews and observing the process on site. During development, the process owner attends the weekly demo and makes decisions; we ask users for brief feedback during testing.

Can we see your reference projects?

We present product concepts instead of a customer reference list: interface designs for fictional companies showing how a particular problem could be solved. To limit risk, we suggest a fixed-fee discovery sprint, repository access from day one and a weekly review of working software.

Which technologies do you use?

We choose technology according to the need and your team's ability to take over. Our default choices are React and TypeScript for web interfaces, Node.js or Go for the backend, and PostgreSQL for the database. If your team knows another stack such as .NET or Java, we may choose it to make handover easier; we decide together during discovery.

Where is our data stored, and how is KVKK addressed?

We set up infrastructure in your cloud account or data centre. If data must remain in the EU, we choose an EU region; if it must stay in Türkiye, we use a provider operating there or your own servers. During discovery, we list which personal data is processed where; role-based access, encryption and audit trails are included in the first release.

Next step

Share the process you want to simplify. We will review your request and clarify missing details by email, then define the appropriate meeting, discovery or pilot scope.

Your own calculation

See how much time your manual process takes

Use the free automation savings calculator to compare monthly workload, potential time savings, and operating costs using the same assumptions. The result is not a quote or a guarantee of cash savings.

Resources

Make the process visible first

Free Excel templates provide a starting point for organising stock, tasks, orders and purchasing. Assess when to move to software alongside the files' scope limitations.