The app you keep describing in meetings
A two-person studio in Athens that designs and builds custom web and mobile apps end to end. You talk to the people writing the code, every week, until it is live.
Everything dark on this page is running software, not a picture of it. The phone is a good place to start.
Spanakopita
Spinach, feta, dill
€3.40
0Bougatsa
Semolina custard, cinnamon
€3.80
0Koulouri
Sesame ring, baked at 05:00
€1.20
0Freddo espresso
Double shot, over ice
€2.60
0
Cart maths, stock limits, and a receipt at the end.
We have no case studies. We have this page.
Most of what we build sits behind a client login, so instead of screenshots of work you cannot verify, everything dark on this page is running code you can reach into and break.
The panel above is a real GPU program
That is a fragment shader compiling in your browser on every edit. Change the 6.0 to a 3.0 and count the arms. Delete a semicolon and it will tell you which line, then keep showing the last frame that worked - which is the kind of detail that separates a demo from a product.
The terminal knows about the studio. Type stack or how.
What we build
Custom software, written for your problem. If a template would genuinely do the job, we will tell you that on the first call instead of billing you to rebuild it.
Web applications
The thing your business actually runs on: dashboards, booking systems, internal tools, customer portals. React and Next.js, typed end to end, deployed somewhere you can afford.
- Next.js
- React
- TypeScript
- Postgres
- Firestore
Mobile apps
One codebase for iOS and Android with Flutter or React Native, or native Swift where the hardware demands it. We handle the store submissions, the certificates and the release process.
- Flutter
- React Native
- Swift
- Firebase
- App Store
Online shops that are not templates
When an off-the-shelf shop cannot model your pricing, your stock or your checkout, we build the parts that matter and connect the rest to what you already use.
- Payments
- Stock
- ERP integration
Rescue and rebuild
An app half-finished by someone else, or one nobody can safely change any more. We read it, tell you honestly whether to fix or restart, and give you the estimate for both.
- Audit
- Refactor
- Handover
Built for a sector, not for everyone
Four markets we know well enough to be useful on the first call. Each page names its own prices, answers its own questions, and has something running on it you can break.
AI automation
Automate the typing, not the judgement
For operations, finance and support teams
Pilot on one process · €6k – €12k
Hotels & hospitality
Every direct booking is a commission you keep
For hotels, villas, rooms and tour operators
Booking engine on your site · €9k – €18k
Restaurants & groups
A restaurant is a floor plan, not a number of covers
For restaurant groups, not for a single taverna
Own ordering and booking channel · €7k – €15k
Maritime & logistics
The spreadsheet the whole chartering desk depends on
For shipowners, managers and freight operators
One spreadsheet, replaced properly · €20k – €40k
Clinics & diagnostics
When the practice outgrew the practice software
For multi-site clinics, diagnostic centres and dental groups
The scheduling layer · €12k – €25k
The work your team should have stopped doing by now
Most companies have a process that runs on someone re-typing things between two systems. That is the work worth automating first - not because it is glamorous, but because it is measurable, and because a model that gets it wrong can be caught before it costs anything.
Documents in, structured data out
Invoices, delivery notes, CVs, contracts, forms that arrive as PDFs and scans. We extract the fields you need, check them against what you already hold, and push a confidence score with every row so a person only reviews the uncertain ones.
- Extraction
- Validation
- Human review
Support that answers from your own material
An assistant grounded in your documentation, past tickets and product data rather than the open internet. It cites where each answer came from, and it hands over to a person when it does not know.
- RAG
- Citations
- Escalation
Processes that run themselves
The chain of steps between two systems that a person currently babysits: triage, routing, reconciliation, follow-ups. We automate the path and leave the approvals where a mistake would be expensive.
- Workflows
- Integrations
- Approvals
How we keep it honest
- Measure before you trust
- Every automation ships with an accuracy number measured on your real data, not a vendor benchmark. If it is not good enough, you find out during the pilot rather than in production.
- A person keeps the expensive decisions
- The model does the reading and the typing. Anything that moves money, signs something, or contacts a customer stays behind an approval until you decide otherwise.
- It says when it does not know
- Low confidence routes to a human instead of guessing. An automation that fails loudly is worth far more than one that is quietly wrong.
- Your data stays yours
- We default to models that do not train on your inputs, and we will run things on your own infrastructure when the data cannot leave it.
Nine weeks from a conversation to something in the App Store
That is the shape of a typical first build. Yours will differ - but this is the rhythm, and you will always know which part of it you are in.
- Day 1
A call, and an honest answer
Forty-five minutes. You describe the thing you want to exist. We tell you whether we are the right people to build it, and say so plainly when we are not.
- Week 1
Shaping
We turn the idea into a scope: what is in phase one, what waits, what the hard parts are. You end the week with sketches and a fixed price. If you stop here, you keep the document.
- Weeks 2–9
Two-week slices
Every slice ends with something you can open on your phone and use. No status decks, no demo environments that only work on our machines. You see the real thing accumulating.
- Launch
Out, then watched
We ship it and stay on call for a month while real users find the corners we did not. After that you either take it in-house - we hand over documented code - or we keep going.
Small on purpose
App Crafters is two engineers. That is not a stage we are trying to grow out of - it is the product. Nothing you say in a call has to survive being relayed to a delivery team, because there is no delivery team.
It also means we take on a handful of projects a year and turn down more than we accept. If your thing is not a good fit for two people, we will say so on the first call rather than three months in.
- Based in
- Athens, Greece
- Working hours
- EET / EEST, overlapping most of Europe
- Team size
- Two, and staying that way
- Typical first build
- Nine weeks
Questions we get asked before the first call
- How much does a custom app cost?
- Most first builds land between €15,000 and €60,000, depending on how much of it is genuinely new. We fix the price for phase one at the end of the scoping week, before any code is written, so you are never signing a blank cheque. A short scoping engagement on its own is a few thousand euros and you keep the document either way.
- How long does it take to build an app?
- A first version that real people can use is usually nine weeks: one week shaping the scope, then four two-week slices. Larger products keep going in the same rhythm. You get something working after every slice rather than waiting until the end.
- Do you build with WordPress?
- No. Most agencies in Athens will build you a WordPress or WooCommerce site, and for a brochure site that is genuinely the right answer - we will say so and point you at someone good. We are for the case where the software is the business: a booking engine, a marketplace, an internal tool, an app.
- Who owns the code?
- You do, once it is paid for - the repository, the design files, the deployment. We hand over documented code and we do not hold hosting or accounts hostage. Leaving should be boring.
- Do you work with clients outside Greece?
- Yes, and most of our work is remote. Athens is EET, which overlaps a normal working day across Europe and gives you a few hours with the UK and the US East Coast. We can meet in person if you are in Athens.
- Can you take over an app someone else started?
- Often, yes. We read the codebase first and tell you honestly whether it is worth continuing or cheaper to restart, with an estimate for both. That audit is a fixed price and you keep the write-up whichever way you go.
- What do you need from me to start?
- A clear description of the problem and one person on your side who can make decisions. Not a specification - writing that with you is the first week's work.
Tell us what you are building
The more specific you are, the more useful the reply. We answer every enquiry ourselves, within a working day.
Or write to hello@appcrafters.gr.