Four lines of work
Four lines of work. None of them is "everything".
Akaunting: installing it, upgrading it, extending it, making it work in Turkey. Tailor-made Laravel and Nuxt business software. A senior developer inside your own team's sprint. And the HR side: software and integrations for HR processes. Everything below is one of those, or a small paid first step into one of them.
The four lines
Start from the problem, not from our service list.
If the accounting system is the problem, that is the Akaunting line. If the problem is a process nobody sells software for, that is the bespoke line. If your own team needs a senior pair of hands for a while, that is the third card. If the problem is an HR process or an HR product, the fourth card.
Self-hosted
Akaunting, run properly
Installation and hardening, upgrades and rescue, private modules the next upgrade cannot delete, and the Turkey side: e-Fatura assessment, tevkifat configuration, a TDHP chart of accounts. You buy and hold your own licence — we sell labour and judgement, never resold licences.
See the Akaunting lineFixed scope, fixed price
Software shaped like your process
Order tracking, field forms, stock, approval flows, reporting — the internal tools that currently live in a shared spreadsheet. Laravel and Nuxt, in a private repository you own from the first commit.
How we buildDays per month
A senior in your sprint
You have a team; it has no Laravel senior, or it inherited a codebase nobody wants to touch. A named engineer for an agreed number of days a month, in your repo and on your board. No subcontractors.
How the days workDomain experience
HR processes and HR software
Close to five years of Tech Lead and CTO experience across recruiting, core HR, payroll inputs and time tracking, and performance. HR software built for your company, integration of HR systems that do not talk to each other, or senior support for teams building HR software.
See the HR lineThe first purchase
Every line starts with something small and paid.
Not a free proposal you have to chase, and not a discovery phase that quietly becomes the project. A bounded piece of work with a written deliverable, credited against the engagement if you continue.
5 business days
Akaunting health check
A written report on your version, your modules, the hosting pre-flight, your backups and your licence-tier exposure — with an upgrade plan and the order to do it in. Credited against whatever follows.
Akaunting servicesTimeboxed, agreed up front
Discovery and fixed quote
We map the process with the people who run it and hand you a scope with acceptance criteria, a fixed price and a date. If you walk away, the document is yours and another studio can quote from it.
How we build1–2 weeks
Technical audit
A read of an existing Laravel or Nuxt codebase, or of an Akaunting install: what will bite you, in what order, and what it costs to fix. Remediation is quoted separately and you are free to give the report to somebody else.
Ask about an auditHow we work
The operating rules, so you can tell what you are buying.
- At most two active builds at a time. When we are full we say so, and give you a date.
- The person who writes the code is the person answering your email. No account manager in the middle.
- No subcontractors. If we cannot do it ourselves we tell you who can.
- Scope, price and duration in writing before anything starts.
- Something you can click every week, instead of a status report.
- Turkish and English, in Turkish business hours.
- Your repository, your server accounts, your data — from the first commit.
- We use AI tools, and a senior developer reviews everything that ships as carefully as a colleague's pull request.
Fit
The engagements we take, and the ones we turn down.
This list has cost us work. It is staying, because the alternative is discovering the mismatch in month three.
Work we take
- A process no packaged product covers, with one internal owner who can make decisions
- An Akaunting install that has to keep working: upgrades, modules, the Turkey side
- Somebody else's Laravel codebase that still has to run while it is being fixed
- A Nuxt or Vue front end on top of a backend that already exists
- A long maintenance relationship where the same people stay on it
- A paid audit whose report you are free to hand to another studio
Work we turn down
- Head-count filling: five seats by Monday, billed hourly against a timesheet
- A fixed price on a specification that will change every week
- Projects where nobody inside can explain how the process actually works
- WordPress theme work and template landing pages
- Unpaid pitch work — mockups or a prototype in exchange for a shot at the job
- Running Akaunting as a hosted service for your own customers: its licence does not allow it, and we will show you the clause
Choosing
What people ask before they pick a line.
We need both — an Akaunting install and a custom tool around it. Is that one engagement?
Usually two, run in sequence, under one written plan. The Akaunting side is productised and priced per package; the custom side needs discovery first. Running them at once is possible and we will say so when it is cheaper for you, but a stuck upgrade and a greenfield build compete for the same attention, and one of them loses.
Do we have to start with the paid first step?
For an Akaunting rescue, no — if your books are down we triage first and assess afterwards. For anything we would put a fixed price on, yes. A fixed price without an assessment is either padded to cover our ignorance or it collapses halfway, and both are worse for you than a small invoice at the start.
Can you work alongside our existing developer or agency?
Yes, and it is common. We ask for one named technical contact on your side, we work in the repository and issue tracker you already use, and we put our decisions where their team can read them. What we will not do is take over a codebase behind its author's back — if that relationship is ending, that conversation is yours to have first.
Where does an integration between Akaunting and our other systems belong?
In the Akaunting line if the work lives inside Akaunting as a module, and in the custom line if the integration is its own service sitting between two systems. The assessment decides, and it is not a matter of taste: a module the upgrade cannot delete has a different maintenance cost from a separate service you can deploy on its own.
What do you not do at all?
Hosting resale, WordPress, mobile-only work with no backend of ours underneath it, and anything where the winning criterion is the lowest day rate. The turn-down list above is the honest version — if your project sits in it, you hear that on the first call rather than after the contract.
Not sure which line you are in?
That is a normal thirty-minute conversation, and sometimes the answer is "neither — buy the packaged product". We would rather tell you that now than in month three.