What exactly does a software company do?

It writes software that does not come ready-made: internal tools, connections between systems that will not exchange data on their own, automation for steps somebody does by hand, and reports that assemble themselves. The starting point is your own process.

What does a software project cost?

The 7-day prototype and the finished app have their prices on this page, under "What you pay, and when". For any other project, the cost is set by the scope, by how many systems have to be connected, and by what keeps running after handover. The figure is agreed with you in writing before the build starts.

How quickly will I see my app?

On day 7 you click through the prototype of your app. A progress link comes within 48 hours of the audit call, with one more for every change, so you watch it take shape before that. The 7 days start once the short written list is agreed on the call and your column headers have arrived. If you go on straight after the walkthrough, the finished app follows about three weeks later, roughly a month from the audit call.

What happens if I don't like the prototype or the finished app?

You pay nothing for what you don't like. Our guarantee is called "Pay only if you like it", and it holds twice. On day 7, in a 30-minute walkthrough, you click through the prototype yourself and say whether you like it, with no payment due before that. A no needs no reason: we stop there, and we delete your data on request. If you like it, we invoice the prototype. If you go on, we build the finished app as we agreed on the audit call, for one flat price, and deliver it about three weeks later. If we start it within 30 days of the walkthrough, the prototype fee counts toward that price. For those 30 days the prototype stays up at no charge while you decide. At delivery you go through the finished app the same way. If you like it, we invoice the rest of its price; if you do not, you pay nothing more, and the code stays with us. When you accept the finished app, you choose Care or Care Plus, billed monthly from delivery, or you take the code and host it yourself. Once the finished app is paid, you can ask for its source code at any time. The prototype's scope is the short written list agreed on the audit call: 3 to 5 lines, each a screen, a role and an action, capped at 5 screens and 2 roles. Anything about the guarantee goes to info@fijisolutions.net.

Who owns the code, the data and the accounts at the end?

For a build that follows the process audit, you do, the code included. The accounts are opened in your own name at the start, so there is nothing to transfer at the end. Your data comes out in a format another system can open, and the written instructions leave with it. If you carry on with somebody else, there is nothing to ask us for. For the 7-day prototype and the finished app, you can ask for the source code once the finished app is paid, at any time after that.

Do I have to replace the software I already use?

Usually not. We propose replacement when the existing system allows no connection at all, and the reason is written into the audit plan. More often the gap is a connection between two systems that each work well on their own, or a small tool between them.

Who actually does the work?

Our founder, Charis Moutafidis. He has worked as a software engineer for more than ten years. Those years cover five sectors: banking, travel, telecommunications, health and online education. Some of that work went through Fiji Solutions, some through Peak Code Consulting, his Swiss company, and some in earlier jobs as a developer. Those sectors describe his own working history.

Prototype 7 days after the audit call. Pay only if you like it.

Book my 30-minute call

The Column-First Build starts from the column headers of the spreadsheet your team runs on. Book a free 30-minute audit call and send us those headers. On the call we talk through what you need. We write down together what the prototype must do, and we agree what the finished app must do.

On day 7 you click through the prototype yourself: a screen for each role, with sample rows made from your column headers. If you like it, you pay for it, and if not, you pay nothing and we stop there. If you go on, the finished app follows about three weeks later, and at delivery you pay for it if you like it.

What you hear every week

And the line you say yourself: "I can't see where everything stands without asking around."

"Where's that order at?"

Everyone edits the same spreadsheet, and people chase each other about where an order or a job stands. The foremen call the office to ask where they go tomorrow.

"We type the same thing in twice."

What goes into the spreadsheet gets typed again somewhere else: into accounting, into an email. Each retype is one more chance for a mistake. A change order gets approved on site and never makes it into the log.

"Who changed this?"

Everyone can open and edit the whole spreadsheet: "Everyone sees everything." Someone sorts one column and breaks the spreadsheet for everyone, and someone else has to find out who changed it.

From the audit call to day 7

Every screen is built around the columns your team already uses.

The audit call

In 30 minutes we see how your spreadsheet runs today and talk through what you need from it. Together we write 3 to 5 lines on what the prototype must do: each is a screen, a role and an action, up to 5 screens and 2 roles. We also agree what the finished app must do. The 7 days start once that list is agreed and your column headers have arrived.

Days 1 to 6: progress links

We build each role's screen from your column headers. A private progress link comes within 48 hours of the audit call, and one more with every change. You watch the prototype take shape and comment when it suits you.

Day 7: Pay only if you like it

In a 30-minute walkthrough you click through the prototype yourself and say whether you like it. A no needs no reason and costs nothing: we stop there, and we delete your data on request. If you like it, we invoice the prototype. If you go on, the finished app follows about three weeks later, built as we agreed on the audit call, for one flat price. At delivery you decide the same way: if you like it, we invoice the rest of its price; if you do not, you pay nothing more, and the code stays with us.

What you pay, and when

Pay only if you like it, at both steps.

The prototype is $2,000. We invoice it when you say yes at the day-7 walkthrough.

The finished app is $7,000 in total. If we start it within 30 days of the walkthrough, the prototype's $2,000 counts toward it, so you pay $5,000 more, invoiced when you say yes at delivery.

When you accept the finished app, you choose one of our two care plans, billed monthly from delivery, or you take the code and host it yourself.

Care, $400 a month: hosting on our AWS platform with backups, bug fixes, up to 2 hours of changes and one 1-hour call a month.

Care Plus, $990 a month: everything in Care, up to 10 hours of changes a month, a weekly call and a direct phone line to your engineer.

What each plan covers, line by line, is on the prototype's page, linked below.

Book my 30-minute call

Everything the finished app includes is on the prototype's page: The finished app shows where every order or job stands.

We take on 3 prototypes a month, so each one gets our full attention. Today's prices are where we start, and they will rise as we grow the team.

Software company in Thessaloniki

Our office is in Thessaloniki.

Location

Nikiforou Ouranou & Minotavrou 15, Building G1, Porto Center, 3rd Floor
Thessaloniki 54627, Greece

See us on the map

Phone

+30 231 107 0108

Email

info@fijisolutions.net

If a website is what you need

Not every business starts with its processes. If what is missing is a website that brings you customers from search, that is separate work, with its own timeline. It has its own page too.

Send us your column headers

Paste the top row of your spreadsheet, the one with the column headers. We read them before the audit call, so the call starts from your own columns.

The audit call takes 30 minutes.

Or book the 30-minute audit call here: Pick a time

Pay only if you like it: at the day-7 walkthrough for the prototype, and again at delivery for the finished app. Nothing is paid before day 7, and a no needs no reason.

Before you ask a software company for a quote

If you have not commissioned software before, the difficulty is rarely knowing what hurts. You have just scrolled past three versions of that. It is knowing what you are actually buying, what stays yours at the end, and why two quotes for the same work are so hard to put side by side.

What a software company actually does all day

We write software that does not exist yet, for a process your business has. The piece that moves an order from one system into another with nobody in between. The screen that shows what is outstanding and who has it. The job that runs every Monday on its own.

It comes in two shapes. One is Custom software development in Greece: internal tools, and the connections between systems that will not exchange data on their own. The other is Data analysis in Greece, for when the same figure comes out three ways from three places, and the deliverable there is one source and one owner per number. Above what a spreadsheet holds we work on Snowflake. Fiji Solutions is a Snowflake AI Data Cloud Select Partner.

We do not do desk support, and we do not take on projects framed as digitising the business.

What you get to keep

For a build that follows the process audit, the honest answer is a list of objects. The source code. The documentation. Your data in a format another system can open. Instructions written for a person: what each piece does, where it runs, what happens when it stops. None of it is held back as leverage.

For a build that follows the process audit, accounts work the same way. The domain, the hosting, the code repository and the tool logins are opened in your own name. Ask for that in writing before work starts, with any supplier, ours included. The answer decides what is still standing the day you stop paying.

The third thing is the right to leave. Every ready-made platform holds something back, so choosing between WordPress, Shopify and something built for you is mostly a decision about what you can carry out later.

How a project starts: two ways in

If your team runs on one shared spreadsheet, it starts with the audit call. In 30 minutes we talk through what you need from your spreadsheet. We write a short list of what the prototype must do, and we agree what the finished app must do.

On day 7 you click through the prototype and decide. Pay only if you like it, at both steps: the prototype on day 7, and the finished app when we deliver it, about three weeks after you go on. When you accept the app, you choose Care or Care Plus, billed monthly from delivery, or you take the code and host it yourself.

If the trouble is a process with no spreadsheet at its center, we start with the process audit: a written map of where your money leaks, yours to keep either way. Then comes the build, with three things in writing before any code is written: what gets built, which number will show that it worked, and the price. If you already know your scope, the build can be bought as a fixed scope: Automate one business process.

Your part in the prototype is the column headers, 30 minutes on the audit call and 30 minutes on day 7. For a build that follows the process audit, we need access to the systems, one person who can decide, and two or three hours with whoever does the job by hand.

What it costs to decide

A cheaper question sits in front of the price: what the process costs you today, in hours, in errors corrected later, and in days spent waiting on somebody. That number comes out of one call, and it makes every later comparison possible.

Two quotes for the same thing differ because they count different things. Ask every supplier for the same lines, then split them three ways: paid once, repeating every year, and paid to somebody else, such as hosting. For a build that follows the process audit, the figure is agreed in writing, against the scope, before anything is built.

The cost is driven mostly by decisions nobody has made yet: who approves what, what happens to the exceptions, and which steps are compulsory. In an online shop that is the platform, the payments, the shipping rules, the customer data and the way back out, all settled before a line of code is written.

When the problem is that nobody finds you

The audit measures what the work costs inside the business. Another leak never reaches the books: the customers who went looking and found somebody else. Between your website and a search result there are three stages, crawling, indexing and ranking, and a site missing entirely has usually not cleared crawling or indexing.

Search work is a list of jobs, and part of that list is outside your control. Anyone promising a position has no mechanism to deliver one. Anyone promising work can list it. Website and SEO for more leads is that list, and the process audit is the way in if you want the numbers before anything else.

Advertising is a separate tool. It does not lift your organic position, and switching it off does not lower it. When your customers are local, local results are judged on their own criteria and fed mostly by your Google Business Profile, a page your customers and Google both write parts of.

How you know it worked

To know it worked, you need a measure of how things ran before. That is why the audit records hours, errors and delays while everything still runs the old way. With no baseline, everyone argues about whether it feels better.

In data work the measurement is the product: a report that assembles itself, a figure with one source behind it, an alert that arrives while the problem is still cheap. To see that at small scale, there is an AI prototype for one use case.

In search, the measurable part lives in Google Search Console, with limits almost nobody spells out: what each report counts, and where the sample stops. In AI answers the picture is thinner still, and a screenshot of one chat is not a measurement, because the same question answers differently for the next person.

Questions people ask before the audit call

What exactly does a software company do?: It writes software that does not come ready-made: internal tools, connections between systems that will not exchange data on their own, automation for steps somebody does by hand, and reports that assemble themselves. The starting point is your own process.
What does a software project cost?: The 7-day prototype and the finished app have their prices on this page, under "What you pay, and when". For any other project, the cost is set by the scope, by how many systems have to be connected, and by what keeps running after handover. The figure is agreed with you in writing before the build starts.
How quickly will I see my app?: On day 7 you click through the prototype of your app. A progress link comes within 48 hours of the audit call, with one more for every change, so you watch it take shape before that. The 7 days start once the short written list is agreed on the call and your column headers have arrived. If you go on straight after the walkthrough, the finished app follows about three weeks later, roughly a month from the audit call.
What happens if I don't like the prototype or the finished app?: You pay nothing for what you don't like. Our guarantee is called "Pay only if you like it", and it holds twice. On day 7, in a 30-minute walkthrough, you click through the prototype yourself and say whether you like it, with no payment due before that. A no needs no reason: we stop there, and we delete your data on request. If you like it, we invoice the prototype. If you go on, we build the finished app as we agreed on the audit call, for one flat price, and deliver it about three weeks later. If we start it within 30 days of the walkthrough, the prototype fee counts toward that price. For those 30 days the prototype stays up at no charge while you decide. At delivery you go through the finished app the same way. If you like it, we invoice the rest of its price; if you do not, you pay nothing more, and the code stays with us. When you accept the finished app, you choose Care or Care Plus, billed monthly from delivery, or you take the code and host it yourself. Once the finished app is paid, you can ask for its source code at any time. The prototype's scope is the short written list agreed on the audit call: 3 to 5 lines, each a screen, a role and an action, capped at 5 screens and 2 roles. Anything about the guarantee goes to info@fijisolutions.net.
Who owns the code, the data and the accounts at the end?: For a build that follows the process audit, you do, the code included. The accounts are opened in your own name at the start, so there is nothing to transfer at the end. Your data comes out in a format another system can open, and the written instructions leave with it. If you carry on with somebody else, there is nothing to ask us for. For the 7-day prototype and the finished app, you can ask for the source code once the finished app is paid, at any time after that.
Do I have to replace the software I already use?: Usually not. We propose replacement when the existing system allows no connection at all, and the reason is written into the audit plan. More often the gap is a connection between two systems that each work well on their own, or a small tool between them.
Who actually does the work?: Our founder, Charis Moutafidis. He has worked as a software engineer for more than ten years. Those years cover five sectors: banking, travel, telecommunications, health and online education. Some of that work went through Fiji Solutions, some through Peak Code Consulting, his Swiss company, and some in earlier jobs as a developer. Those sectors describe his own working history.