SOFTWARE STUDIO
ISTANBUL ·41.0082° N28.9784° E
WORKING SOFTWARE.
We build the web, mobile and AI systems your business runs on. One team from discovery to deployment, one point of responsibility.
Start a project01WHAT WE DO
WE DO THREE THINGS. WE FINISH ALL THREE.
-
SOFTWARE DEVELOPMENT
Web, mobile and backend. A product from scratch, or a module on a running system.
- WEB APPLICATIONS
- MOBILE APPLICATIONS
- BACKEND AND INTEGRATION
- TAKEOVER AND MAINTENANCE
FIG. 01 — DEVELOPMENT -
ARTIFICIAL INTELLIGENCE
We connect language models to real workflows: document search, automation, assistants.
- INTERNAL ASSISTANT
- DOCUMENT PROCESSING
- WORKFLOW AUTOMATION
- COST AND PRIVACY
FIG. 02 — AI -
CONSULTING
We sit next to your team: architecture decisions, code review, technical direction.
- ARCHITECTURE REVIEW
- CODE REVIEW
- TEAM AUGMENTATION
- TECHNOLOGY SELECTION
FIG. 03 — CONSULTING
02HOW WE WORK
FOUR STEPS. FOUR OUTPUTS.
- 01
Discovery
We write down the problem and the constraints together. Output: scope, a risk list, a schedule we can keep.
- 02
Design
Screens and data model first. You see what you are getting before any code is written.
- 03
Development
Two-week cycles. At the end of each one you try the working build yourself.
- 04
Deployment
Release, monitoring, backups, handover. The source code and the infrastructure stay in your name.
03WORK
WORK WE HAVE SHIPPED.
We do not name clients without permission. The work says enough.
-
01 FLEET MANAGEMENT · 2026
Fleet tracking on your own server
TypeScript · React · Map layer · PostgreSQL
FIG. 04 — FLEET -
02 VEHICLE TRACKING AND INSTALLATION · 2026
Bulk command automation for GPS devices
Python · FastAPI · PostgreSQL · React
FIG. 05 — SMS -
03 FIELD SERVICE · 2026
Progress billing that moved out of spreadsheets
React · Express · SQLite · Node.js
FIG. 06 — PROGRESS BILLING
04OUR OWN PRODUCT
WE BUILD OUR OWN PRODUCT TOO.
Bilgitch brings a student's study plan, session log and coach conversation into one app. We pay for the decisions we recommend to clients here first, in our own product.
SCREEN — TODAY
The day's plan and routines on one screen. The student knows what to start with.
SCREEN — FOCUS
A study timer. Time spent and questions solved are logged per topic.
SCREEN — ANALYSIS
Mock exam results: net score and topic breakdown. Coach and student look at the same data.
05CONTACT
TELL US THE BRIEF.
Write even if it is still an idea. In the first call we work out the scope and a rough budget together.
FREQUENTLY ASKED
-
How do you price a project?
We do not quote before the scope is clear. First comes a short discovery — a few conversations and a scope document; then a written, itemised quote. If you decide at the end of discovery not to build it with us, the scope document is still yours.
-
How long does a project take?
It depends on scope; there is no single honest answer. We give the schedule at the end of discovery and work in two-week cycles — you try a working build at the end of each one, so whether the schedule holds becomes visible along the way rather than at the end.
-
Who owns the source code?
You do. Source code, servers and store accounts are opened in your name and stay there. At handover you get the repository, the setup steps and the documentation; if another team takes over later, nothing is in their way.