mixanourgiki.gr
A full site with a complete backend behind it. The client administers it themselves at admin level, without coming back to us for any of it.
Sites, web applications, and the software a business runs on behind them — designed, built and kept running by the people who scoped them. Every price we can publish is published, so you can find your figure before you speak to anybody.
An agency’s price carries account managers, offices and a sales floor, and a great deal of the market is built on tooling that guarantees somebody has to come back and fix it. We carry none of that and we build efficiently, so the number is lower. Senior hands write it, the build is the full one, and the security is the same at every price on the ladder.
The people who scope the work are the people who write it. Nothing is handed to a team you have never spoken to.
Domain, DNS, business email, hosting, certificates, the site and the systems behind it. One email address, one invoice.
Architecture chosen so the thing is still maintainable in its third year, by us or by whoever comes after us.
We work daily, weekends included, and the reply comes from somebody who can actually answer the question rather than from a queue.
What it costs to have it built, what it costs to keep it running, what it costs to put an assistant on top — and, past the ladder, software scoped in writing before there is a figure at all. Every kind of build carries a starting price, so you can find your step without talking to anybody first.
Every site we build, from a single page to an enterprise system, on one price ladder.
Read the scope →[ 02 ]What it costs to keep it running afterwards. Three monthly tiers, published.
Read the scope →[ 03 ]Grounded assistants and automation, attached to a build. Scoped in writing before any figure.
Read the scope →[ 04 ]Applications beyond the web — the tool a business runs on. Scoped in writing before there is a figure.
Read the scope →Seniority, architecture and one point of contact: three reasons to choose a small studio over an agency, all of them about what happens after launch.
Most of what makes software expensive later is decided in the first fortnight. Those decisions are made here by the people who will have to live with them.
Anyone can ship a launch. The question is what it costs to change it once real data and real users are in it — and that is a design decision, not a maintenance one.
No handing you to a hosting provider, a domain registrar and a plugin vendor and calling it support. It is all run from one place, by the people who built it.
Four stages, the same on every project. You can read all of them before you commit to anything, and you know what you are getting at the end of each.
Live sites, at their real addresses — open them and judge for yourself. Full builds with a complete backend, where the client administers the site themselves.
A full site with a complete backend behind it. The client administers it themselves at admin level, without coming back to us for any of it.
The same again: a full build with a complete backend and administrative control in the client’s hands. Everything on the site is theirs to change.
Care and Active are the two monthly retainers that keep a site alive after launch. Software rots quietly: certificates lapse, dependencies age, a form stops delivering and nobody notices for a month.
By making the risk readable. Every service page carries the written process and the boundaries of the work before you pay anything, and the first stage of any engagement produces a written scope you can take elsewhere if you do not like it. A portfolio tells you what someone did for a different business; the scope tells you what will happen to yours.
It depends on what the site has to do. A single page and a system with accounts, roles and integrations behind it are different amounts of work, so they are different figures — the Websites page publishes a starting price for every step of the ladder, so you can see roughly where you land before you speak to anybody. Past the ladder the scope decides the number, and we say that rather than print an average.
We can, and in most cases we would rather rebuild it. Two reasons, and the second is the one nobody mentions: you get a current image instead of an inherited one, and you get a site whose security was designed in rather than bolted on. Most of what we are handed was built without anyone thinking about that at all, and patching it afterwards is slower and less certain than building it right. We will tell you honestly if the existing thing is fine and you do not need us.
Yes, and it is the point rather than an add-on. Domain, DNS, business email, hosting and certificates are run by the same people who built the site — one email address and one invoice, instead of three vendors who each blame the other two.
The same thing that happens on a Tuesday. We work daily, we answer at weekends, and there is no queue that opens on Monday. Monitoring raises it, a person looks at it, and you hear about it from us rather than from a customer.
Yes, and from the data model outward rather than translated over the top — locale URLs, hreflang, and a language switch that lands on the same page rather than the home page. Language is not a constraint on who we work with; this site is a working example of the mechanism.
No sales pressure and no generic proposal. Tell us what you are trying to build and you will get a straight technical read on it and a clear next step.
A paragraph is enough to start. If it is not something we should be doing, we will say so and point you somewhere better.