Skip to content
App Crafters

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.

live
  • Spanakopita

    Spinach, feta, dill

    €3.40

    0
  • Bougatsa

    Semolina custard, cinnamon

    €3.80

    0
  • Koulouri

    Sesame ring, baked at 05:00

    €1.20

    0
  • Freddo espresso

    Double shot, over ice

    €2.60

    0

Cart maths, stock limits, and a receipt at the end.

Try it on your own numbers

One of the tools from the sector pages. A hotel or villa owner puts in rooms, rates and what the OTAs take, and it says what direct bookings are worth and whether a build pays back - including when it does not.

The full page for hotels
  1. Start from a property like yours, or set your own rooms and rate.
  2. Drag the share you would win direct and watch the payback move.
  3. On the availability rules tab, try a stay an off-the-shelf engine would accept.

0/3

commission-benchinteractive

Start from

Room nights sold
3,125
Annual room revenue
€296,856
Paid to OTAs15.4% of all room revenue
€45,716
Revenue moved to direct
€41,560
Commission not paid
€9,143
Less card processing
− €623
Payback against the share you win directShare won direct
0%30%60%two seasons9%
crosses two seasonsyour assumption

At 20% you are already past the crossing. The assumption has room in it, which is the comfortable place to be making this decision from.

Net gain per year

€8,520

Build pays for itself in

9.9 months

Inside a single season. This is the easy version of this decision.

Real arithmetic, running in your browser, on figures you control. Nothing is sent anywhere. The defaults are industry ranges, not your property - change them.

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
    See project
  • 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
    See project
  • 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 plainly whether to fix or restart, and give you the estimate for both.

    • Audit
    • Refactor
    • Handover

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.

  1. Day 1

    A call, and a straight answer

    Twenty 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.

  2. 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.

  3. 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.

  4. 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, and here they are by name. 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. When something is too big for two people to build at the pace it needs, we bring in engineers we have worked with and watched ship - and we tell you who, before they start. The decisions and the architecture stay with the two of us. What we will not do is hand you to a team you have never met.

Based in
Athens, Greece
Working hours
EET / EEST, overlapping most of Europe
Who decides
The same two, on every project
Typical first build
Nine weeks

Questions we get asked before the first call

How much does a custom app cost?
Each sector page publishes its bands: a first project usually lands between €3k and €12.5k, and a system that replaces a whole spreadsheet-run office €10k to €20k. The order is always the same: a scoping week first, priced on its own, ending in a written scope and a fixed price for phase one before any code is written. You keep that document either way, so if you stop there you have something you can take to anyone.
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 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.

Pick a time that suits you

Twenty minutes, by video. You describe what you want to exist; we tell you whether we are the right people to build it.

  • No sales call and no deck - the two people who would do the work are the two on the call.
  • Bring a rough idea or a finished spec. Either is fine, and the first week exists to turn one into the other.
  • You leave with a clear answer about scope, cost and whether it is worth doing at all.

Would rather write it down first? Use the form.

Loading the calendar. Open it in a new tab.

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.

What it does, who it is for, and when you need it.

Rough budget

A rough range saves us both a call. Optional.

Or grab a slot in the calendar