Internal software that connects your tools and removes manual work.

Custom software built around the way your business runs: integrations, internal tools and workflows with your rules built in.

Fixed scope. Fixed price. Agreed in writing before development starts.

Which of these sounds familiar? Each starts with a written reply and, if it’s a fit, a fixed‑price proposal.

“Our team copies the same data between the CRM, accounting and spreadsheets every day.”

Your systems are connected through their APIs, so data is entered once and arrives where it’s needed: checked, in the right format, without anyone retyping it.

“Our reports are built by hand from exports, and nobody fully trusts the numbers.”

Figures pulled directly from your systems and updated automatically. One source, no weekly spreadsheet rebuild.

“We’ve tried several platforms. None of them matches how we actually work.”

An application built around your process: your steps, your approvals, your terminology. Your team uses it because it is faster than the workaround.

Built for the people who use it every day. Not consumer apps: working tools for your staff, and every one includes the same six parts.

The data model

Your business rules expressed as a clean database structure: no duplicates, no broken references.

The integrations

Direct API connections to your accounting, CRM, ERP and communication tools. Data flows once, in the right direction.

The logic

Your procedures turned into automated steps, validation rules and notifications.

The controls

Roles and permissions, plus a log of who changed what and when.

The interface

Clear screens designed for speed and accuracy in daily use.

The documentation

How it works and how to run it, so any developer can maintain it after me.

How a project runs. Scope and price agreed before development.

  1. Your enquiry

    My written reply within 2 working days: questions, a suggested approach and an indicative price range. If existing software already solves the problem, I’ll tell you which.

  2. Specification

    A fixed-fee stage of 1⁠–⁠2 weeks to define the features, data, integrations, what is not included and the acceptance criteria. It ends with a fixed price and timeline, and the document is yours either way.

  3. Build in milestones

    Each milestone is delivered to a test environment and shown to you working. The source code lives in your repository from day one.

  4. Acceptance

    Each milestone is tested against the criteria agreed in the specification. Once you confirm acceptance in writing, the milestone is invoiced.

  5. Launch and support

    Deployed to your accounts and infrastructure. Defects are fixed free of charge for 60 days after acceptance. Ongoing maintenance is available under a separate monthly agreement.

No surprises. Everything on paper.

  • [ Scope ]

    Written specification.

    Including a list of what is out of scope.

  • [ Price ]

    Fixed price per stage.

    New requests go into a written change request with their own price, never quietly added.

  • [ Payment ]

    Milestone payments.

    40% to start, the rest invoiced per accepted milestone, paid by bank transfer.

  • [ Ownership ]

    You own the code.

    Full rights transfer to you on payment. Open-source parts only under MIT, Apache 2.0 or BSD licences.

  • [ Support ]

    Warranty.

    60 days of free defect fixes after acceptance.

  • [ Privacy ]

    Confidentiality.

    NDA signed before you share details, on request.

Your systems stay yours. Your accounts, your data, your rules.

  • Your accounts.

    Hosting, repositories and services in your company’s name.

  • Minimum access.

    Only the permissions needed, removed when the project ends.

  • Test data first.

    Built on test data; production data only where necessary.

  • No third-party AI.

    Never on your data without your written consent.

You work directly with the engineer who builds it. No account managers, no hand‑offs. The person who writes the specification writes the code. Working remotely with clients worldwide, in English.

Frequently asked questions. Short answers to what usually comes up before a project starts.

How much does a project cost?

It depends on scope. You get an indicative range in my first reply and a fixed price after the specification.

How long does it take?

The specification usually takes 1⁠–⁠2 weeks. Most builds take 4⁠–⁠12 weeks.

Who owns the code?

You do. Full rights transfer on payment, and the code lives in your repository from the start.

What if our requirements change?

Changes are written up as a change request with their own price and timeline. Nothing is added silently.

Can you work with our existing systems?

If they have an API or a reliable export, yes. The specification confirms this before you commit to the build.

What happens after launch?

60 days of free defect fixes, then optional monthly maintenance.

How do contracts and payments work?

A written contract, an invoice for each milestone, payment by bank transfer.

What about time zones?

I work on GMT+4, which overlaps with Europe, the Middle East and much of Asia. Most communication is written, so nothing gets lost.

Send me the problem. Don’t prepare a technical specification. Describe what slows you down: what breaks, who is involved, which systems are affected. I’ll read it myself and reply in writing within two working days.

Your message comes straight to me. You won’t be added to any mailing list. Privacy Policy

Or message me on WhatsApphello@glebmenshov.com