How it works

A clear path from a first conversation to a working system.

No open-ended hourly billing and no vague promises. Paid work starts only with a written scope and a fixed price, and every milestone ends with something you can see working.

  1. A free first conversation

    Write to me through the form, by email or on WhatsApp, and we talk it through in writing or on a call. You get a straight answer on whether data science or AI will help.

    No cost, no commitment. If a spreadsheet or an off-the-shelf tool would do the job, I will say so.

    Time
    A 30-minute call or a few messages
    Cost
    Free
    Get in touch
  2. A fixed-price proposal

    A short written proposal: the scope, what is not included, the milestones, the timeline and a fixed price for each stage.

    You know the price before each stage starts. Extra requests get their own quote, never a surprise invoice.

    Time
    Usually within a week of our first talk
    Cost
    Free, with no obligation to accept it
  3. A pilot on your real data

    We start with a small, paid first step that proves the idea on your own data, usually in a few weeks. For example, a sales forecast for one product line before the whole range.

    You see working results early, with their limits stated plainly. Then you decide: stop there, adjust, or go ahead with the full system.

    Time
    Usually a few weeks
    Cost
    Fixed price, set in the proposal
  4. Build, deploy and hand over

    If the pilot works, the full system is built: the same idea extended to everything in scope, deployed where your team uses it and documented. You own the code once it is paid for.

    Then an optional monthly support plan keeps it running, monitored and improving.

    Time
    Depends on the scope, with a date for each milestone
    Cost
    Fixed price, agreed after the pilot
What you pay for

What is free, and what is paid.

Nothing is billed by the hour, and no paid work starts without its price in writing.

  • Free

    No cost and no commitment

    • The first conversation, by call or messages
    • The written proposal, with the scope, timeline and price
    • Fixes for 30 days after handover, if something in the agreed scope does not work as described
  • Fixed price

    Agreed in writing before each stage starts

    • The pilot on your own data
    • The full system: building, deployment, documentation and the handover session, as listed in the proposal
    • Changes and extra requests, each with its own short quote
  • Optional, monthly

    A fixed monthly fee, never a condition of the project

    • Hosting and monitoring
    • Updates and retraining on new data
    • Small changes and improvements
  • Running costs

    Paid to the providers, usually from your company’s own accounts

    • Cloud hosting
    • AI services such as OpenAI, when used
    • Estimated in the proposal, before you agree
In every contract

Simple terms, written down before work starts.

  • Scope and exclusions

    What will be built, and just as clearly, what is not included.

  • Payments

    A fixed price for each stage: 30 to 50% upfront, the rest at milestones, against Kalson FZE invoices.

  • Milestones

    Visible checkpoints, each with something you can see and test.

  • Changes

    New requests get a short written quote before any extra work starts.

  • Ownership

    The code and the work are yours once the project is fully paid. No licence fees, no lock-in.

  • Confidentiality

    Your data stays private and is returned or deleted at the end. NDA on request, and a GDPR data processing agreement for clients in Europe.

FAQ

Common questions.

Something else on your mind? Just ask.

Get in touch

Getting started

How much does a project cost?

A fixed price for each stage, agreed in writing before that stage starts. It depends on what you need: an analysis, a trained model or advice costs far less than a complete system that is deployed and maintained, and you pay only for what the proposal lists. The first step is a free conversation.

How can we judge your work before starting?

Look at the projects: each one has a demo recorded from the running app, the code and the results. Then start with a small fixed-price pilot on your own data, so you see real results before committing to more. Payments follow milestones you can check, and every project has a written contract with Kalson FZE, a licensed UAE company.

What if the pilot does not give good results?

Before the pilot starts, the proposal states what a good result means for you, such as forecast accuracy, hours saved or the share of documents read correctly. If the pilot falls short, you have paid for a small pilot, not a full system, and you get a written summary of what was tested, what your data showed and whether another approach is worth trying. You are never committed to the next step.

Do we need a lot of data?

Less than you might think. Many useful projects start with a year or two of sales, a folder of PDFs or an export from your ERP. On the first call I will look at what you have and tell you whether it is enough.

What do you need from our team?

Very little. One person who knows the process and can answer questions, access to the data (an export is often enough to start), and a short review at each milestone to look at the results and give feedback. You do not need a technical team.

Can you work with our existing systems?

Yes. I can work from exports or APIs of ERPs and CRMs (Odoo, Zoho, SAP Business One, Microsoft Dynamics and others), online stores, point-of-sale systems, databases, spreadsheets and PDFs. The goal is to fit into how your team already works.

How long does a project take?

A focused pilot usually takes a few weeks. A full system takes longer, depending on the scope. The proposal gives a timeline with milestones so you always know what comes next.

Money and ownership

What are the payment terms?

Part of the price is paid upfront (30 to 50%, set in the proposal) and the rest at agreed milestones, against a Kalson FZE invoice. If a payment is late, work simply pauses until it arrives.

What will it cost to run each month?

The proposal estimates the running costs before you agree to anything: cloud hosting and, when used, fees for AI services such as OpenAI. I design to keep them low, for example by using a smaller AI model where it is accurate enough. The accounts can be in your company’s name, so you see every bill, or be managed for you under the monthly support plan.

Who owns the code?

You do, once the project is paid in full. You receive the source code and everything else the proposal lists, such as documentation or deployment scripts, with no licence fees and no lock-in.

Data and language

Is our data safe?

Your data is used only for your project. I can sign an NDA before you share anything, work with anonymised samples first, and keep data on your own servers or cloud account when needed. For clients in Europe, Kalson signs a data processing agreement under the GDPR. When an AI service such as OpenAI is used, I explain exactly what is sent and choose settings that do not use your data for training. At the end, your data is returned or deleted, as agreed in the contract.

Can the AI work in Arabic?

Yes. Current language models read and write Arabic well, so documents, assistants and product content can be bilingual. I test on a sample of your real Arabic material before promising any accuracy.

Where do you work, and in which languages?

Kalson is based in Sharjah, UAE. Meetings can be in person in the UAE, and I can work remotely with companies anywhere: across the Gulf, in Europe and beyond. I work in English and French.

Working together

Will we work with you directly?

Yes, from the first call to delivery, so nothing gets lost between a salesperson and a developer. When a project needs extra skills, such as design or mobile development, I bring in specialists under the same contract and remain your single point of contact.

What if you are unavailable?

Your system never depends on me alone. Everything is built with standard, widely used tools, in clear code another engineer can read, so your own team or someone else can take it over. Planned time away is announced in advance, and any change to milestone dates is agreed in writing.

What happens after delivery?

You get the handover agreed in the proposal, for example documentation and a walkthrough for your team. For 30 days after handover, anything in the agreed scope that does not work as described is fixed free of charge. An optional monthly support plan then covers hosting, monitoring, updates, retraining and small changes. It is never required: the code is yours, so your own team or another engineer can run it.

Ready for step one?

Describe the problem in a few sentences, by message or on a call. I usually reply within one working day, with an honest view on whether it is worth doing.

Send a message

Free first conversation, no commitment.