OSBSA Bilişim
en

Web development and custom applications

A brochure site shows information. This is a different job: we write an application that takes orders, draws down stock, produces quotes and decides who gets to see what. If you have a process running on spreadsheets, this is probably what we'll be talking about.

You may not need this

Custom development is expensive and not every company needs it. If your site shows information, collects forms and carries a blog, an off-the-shelf content management system will do the job. Saying that doesn't help our sales, but correcting the wrong investment later costs more.

Here's the dividing line: does the site have rules, or only content? If there's no price, permission or calculation that changes from one user to the next, you can stop reading here.

How is this different from design?

On a brochure site, changing a page means changing the text. Here, changing one rule affects every screen, permission and report tied to that rule.

So half the work isn't coding, it's getting the rules written down correctly. That's also why we don't quote before a scope document exists.

The two kinds of work compared
Brochure siteCustom application
OutputPages that present informationAn application that does work
DataText and imagesOrders, stock, users
UsersVisitorsVisitors and authorised users
Measure of complexityNumber of pagesNumber of business rules and roles
Testing loadAppearance and formsRules, permissions, data integrity
MaintenanceUpdating contentChanging rules, managing releases

What do you build it with?

We choose against three questions: will it still be supported in years to come, can you find a developer to take over, and can search engines read the content without running JavaScript?

The stack we use
LayerChoiceWhy
LanguageTypeScriptCatches mistakes as you write rather than at runtime; keeps the code readable for whoever takes it over
Application frameworkNext.js and ReactPages render on the server, the first load is fast, search engines see the content directly
Server sideNode.js, Server Actions and API routesOne language and one repository for front and back; integration costs drop
DatabasePostgreSQL or MariaDBTransactional guarantees, relational integrity, supported by most hosting
Data accessPrismaSchema in one file, migration history you can follow, less exposure to SQL injection
ValidationZodThe same rule runs in the form and on the server
SessionsSigned cookies, passwords stored with bcryptNo plain-text passwords, permissions checked on the server
InterfaceOur own component set on Tailwind CSSNo theme dependency, unused styles aren't carried around
FilesS3-compatible storage, AVIF and WebP conversionLarge files don't tie up the application server
DeploymentGit, automated builds, a separate test environmentA bad release can be rolled back; nobody copies files onto production by hand

What we don't use belongs on the list too: Flash, FrontPage, Fireworks and classic ASP appear in none of our current projects. If your site was built with those, the work isn't an update, it's a rewrite.

What kind of work do you take on?

  • Dealer and service portals: pricing by role, order entry, account tracking
  • Product catalogue and technical document management, variant and dimension tables
  • Quote workflows: from a form to a PDF quote, with approval and revision tracking
  • Booking and appointment systems, with capacity and reminders
  • Internal admin panels: requests, tasks, documents, permissions
  • Integrations: ERP, bookkeeping, shipping, e-invoicing, virtual POS, marketplaces
  • Takeovers: code review, documentation, staged renewal

How does an integration get built?

An integration means two systems talking to each other so the same data doesn't get typed in twice. This is where projects stall most often: the other side's documentation is incomplete, field names don't line up, and nothing says what happens when something fails.

So we split the job in three. A field mapping table: which field corresponds to what. Failure cases: what happens if the connection drops or the data is rejected. And retry logic. We don't start writing code until all three are written down.

  • ERP and bookkeeping: product, stock, account and price transfer
  • E-invoicing and e-archive: issuing documents through an integrator
  • Shipping: creating consignments, barcodes, matching tracking numbers
  • Payment: virtual POS or a payment provider; card data never reaches us
  • Marketplaces: product and stock synchronisation, pulling in orders

What do you do about security?

Security isn't a separate module, it's a habit applied at every step. These are our minimum rules:

  • Everything arriving from a browser is validated again on the server; client-side checks are a convenience, nothing more
  • Passwords are hashed with bcrypt and never stored as plain text anywhere
  • Permissions are checked on the server; a hidden button is not a permission boundary
  • Rate limiting, a honeypot and bot verification on login and form endpoints
  • Parameterised database queries, type and size checks on file uploads
  • Card data never lands on our server; it stays inside the payment provider's frame
  • A data inventory, retention periods and a deletion procedure, as required by KVKK (Turkey's data protection law)
  • Once backups are set up, a restore is actually attempted; an untested backup isn't a backup

Who ends up owning the software?

The system runs in your name: the domain is yours, the panel access is yours, the data inside it is yours. You can export your product, customer and order records whenever you like. You don't pay us an annual licence to keep the site switched on.

Transferring the source code is a separate conversation. The real cost of software isn't running it, it's designing, writing and documenting it, which is why code transfer isn't inside the package price. Clients who want it raise it in the meeting and we put the price and the scope in the contract. We say this up front so there's no surprise later.

Once code transfer is agreed, the handover file contains the Git repository, a database backup and the schema files, the list of environment variables, the third-party service accounts, an installation guide and a list of known gaps. We write that last item out deliberately. No software is handed over complete; the honest thing is to put the gaps on paper.

How we work, in seven steps

Every step ends with something concrete in your hands, so you never have to guess which stage the job is at.

  1. 01

    Discovery call

    We talk about what you sell, who you sell it to and what you want the site to do. If you already have one, we go through it together on screen. You end up with a written note of what's needed.

  2. 02

    Quote and contract

    Scope, delivery time, revision rounds and price, all in writing. The same document shows what isn't included, because we'd rather both sides picture the same job when they sign.

  3. 03

    Content and page structure

    We map out the pages and take stock of the text and images. Where content is missing, this is where we settle who writes it.

  4. 04

    Design

    The home page comes first; once you approve it we move on to the inner page templates. This is the stage to ask for changes: the design is frozen once the build starts.

  5. 05

    Build

    Coding, admin panel, forms and integrations. You get a preview address, so you can open it and see where the work stands without asking us.

  6. 06

    Testing and launch

    We go through speed, the layout on a phone, accessibility, the form flow and the redirects from your old addresses one by one. Nothing goes live until that list is clear.

  7. 07

    Handover and follow-up

    We walk the panel with you and set up Search Console and analytics ourselves. For the first stretch after launch we keep an eye on your rankings and error logs too.

Packages

All

Starter

The minimum setup for being visible

No fixed price

Two things set the price: how many pages there will be, and who writes the text. We don't quote a figure before talking through both.

  • A site that explains what you do: home page and inner pages
  • Customers looking on a phone can read it without zooming
  • Form submissions land in your inbox, and there's a WhatsApp button
  • Directions to your address open from the map in one tap
  • You change text and images yourself from the admin panel
  • No "not secure" warning in the browser address bar
  • Searches for your company name show the right title, description and address on Google
  • You can see who came from where in Search Console and Analytics
  • Images are resized and converted, so pages don't stall on mobile data
  • Pages that work with a keyboard and with a screen reader
  • On handover we walk the panel together; the domain, the panel and the content stay in your name
  • Blog and news section
  • Product catalogue and technical specification tables
  • A second language
  • Basket, payment and order tracking
  • Software written specifically for you
See what's included
Recommended package

Business

For companies with a catalogue and a steady flow of content

No fixed price

The price moves with how many products you'll be entering and where the design starts from. Come in with your catalogue and we'll count the items together.

  • Everything in the Starter package
  • Not an off-the-shelf theme but a design drawn for you: you won't look like your competitor
  • Product and service catalogue: categories, specification tables, downloadable PDF documents
  • A blog: every article you publish opens another door in search
  • Your past work written up as case studies, so the reference question is settled in the meeting
  • A quote form that moves step by step, so nobody gives up at the sight of a long form
  • FAQs marked up so they can appear in Google's answer box
  • Each page's title and description set separately, so your pages don't eat each other's rankings
  • Your old addresses redirected to the new ones, so your Google position doesn't reset
  • Speed as a delivery condition: on slow 4G, LCP under 2.5 s · INP under 200 ms · CLS under 0.05
  • Where visitors got stuck, tracked with heat maps and session recordings
  • An llms.txt file and a crawler policy, so AI tools read your site correctly
  • A second language
  • Basket, payment and order tracking
  • Dealer portal and external system integration
See what's included

Professional

When you need selling, dealer management or integration

No fixed price

The number of integrations sets the price. An accounting connection is one job on its own, a shipping connection another; we work out in discovery which ones you actually need.

  • Everything in the Business package
  • Basket, orders, stock and coupons: selling runs through the site
  • Card payments taken with 3D Secure, with card details never touching your server
  • Shipping connection: the tracking number attaches itself to the order
  • Dealers, customers and staff get separate permissions, so nobody sees what they shouldn't
  • Dealer-specific price lists visible only to a logged-in dealer
  • A second language: visitors from abroad read it in their own
  • Data exchange with bookkeeping, ERP and e-invoicing systems (with a field mapping document)
  • Distance selling, returns, delivery, data protection and cookie texts supplied ready
  • Product pages can appear on Google with price and stock information
  • Which product sold how much, which customer bought what: reports from the panel
  • Changes are tried in a test environment first, so live selling never stops
See what's included

Bespoke

Work that doesn't fit a package

If your business rules are non-standard, if several systems have to talk to each other, or if existing software has to be taken over, the package logic stops working. We produce a technical scope document first and price against the items in it. The scoping meeting is free.

Request a scoping meeting

You won't see figures on this page. A price given before the scope is discussed either covers too much or too little. In one conversation we settle the scope and send a written quote the same day, with every item on its own line.

Frequently asked questions

All questions

What does a company website cost?

Four things set the figure: how many different page templates you need, whether we build the design from scratch, whether we write custom software for you, and who writes the text. We don't publish a price list on the site, because a number quoted without knowing the scope always covers either too much or too little. Give us one call to go through those four and we'll send the written quote the same day. What each package covers is listed item by item on /paketler.

Why do quotes for the same job differ so much?

Because the quotes aren't describing the same job. One may be for installing a ready-made theme, another for an interface and custom software built from scratch. Before you compare them, ask both sides four questions: is a theme being used, how many revision rounds are included, who writes the text, and who keeps the code after handover. If the answers don't match, there is no point lining up the numbers.

What does the site cost each year once it's live?

The fixed ones are the domain renewal and the hosting fee. The SSL certificate is free on most setups, so it doesn't become a separate item. The rest is optional: a maintenance agreement, monthly search engine work, an advertising budget. We go through which of those you actually need in the first call and write each one into the quote as its own line.

Is a maintenance agreement compulsory?

No. Your site runs without one and you change the content from the panel yourself. The difference is this: with maintenance, the updates, backup checks and security patches happen without you noticing. Without it, you call us when something goes wrong and pay per job.

How much budget should I set aside for Google Ads?

That comes down to the cost per click in your sector, and sectors differ a lot. Once we open your account and look at your keywords, we can give you a realistic range within a day. One thing to settle from the start: the advertising budget goes straight to Google from your own account, and what we earn is the management fee.

Let's work out the scope together

Tell us which process you want to move onto a screen; we'll draft the screen list, data model and business rules, then price it. This conversation is free.

Get a quoteMessage us on WhatsApp