Skip to content
The 5-Day Build

First working version in 5 working days.

A fixed scope. A fixed price. Working software running on your systems at the end of five working days — not a prototype, not a slide deck.

Fixed price for the agreed scopeFull source code in your repository from day one30 days of fixes included after handover

Who this is for

Agencies and service businesses with a specific, time-costing problem.

You have one clear manual task

Copy-paste between tools, manual screening, chasing updates. One specific thing eating your team's time every week.

You want working software, not a proposal

You have been quoted discovery phases and six-week timelines before. You want to see working code instead.

You can define the scope before we start

The build begins only after the scope is agreed in writing. If the problem is not yet clearly defined, the call is the place to define it.

You are the decision-maker

No procurement process, no committee. You can approve scope and make the first payment yourself.

Budget of around $1,500

That is the fixed price for this engagement. Not an estimate. Not a starting point for negotiation.

You can supply assets and access on time

We need access to your systems, your API keys, and any content on day one. Delays from your side affect the five-day schedule.

What we build

Automations and internal tools for one focused job.

The 5-Day Build is not a platform or a product. It is one focused piece of working software that removes a specific manual task from your week.

Lead / application screening

Reads incoming CVs or leads, scores them against your criteria, surfaces the ones worth reviewing.

CRM or spreadsheet sync

Moves data between your CRM, your spreadsheet, and your inbox without a human copying it.

Status update automation

Pulls status from your project tool and sends a formatted report to Slack or email on a schedule.

Document or report generation

Takes structured input and produces a formatted PDF, a populated template, or a draft email.

Internal dashboard or admin tool

A simple interface for your team to view, filter, and act on data without needing a developer.

API integration or webhook handler

Connects two services that do not natively talk to each other, triggered by an event in either one.

Scope

What you get. What you do not get.

Included

  • Working software running on your systems — not a prototype
  • Full source code in your own repository from the first commit
  • A written update at the end of every working day
  • A recorded handover call so your team can operate it without us
  • 30 days of bug fixes after handover — no hourly billing
  • Basic documentation covering setup, environment, and operation

Not included

  • Features not in the agreed written scope
  • Design work (UI/UX design is quoted separately)
  • Third-party API costs or hosting fees you incur
  • Ongoing maintenance after the 30-day fix period
  • Changes to scope after the build has started
  • Anything dependent on third-party services, API access, app-store review, or external approvals that are outside our control

The process

Four steps. Nothing hidden.

01

Call

30 minutes. You describe the task that is costing your team time. We tell you honestly whether a 5-Day Build can fix it. If it cannot, we will say so and suggest an alternative.

02

Scope

We write up exactly what we will build: features, acceptance criteria, what counts as done. You approve it in writing. The price and delivery date are fixed at this stage. Nothing starts until you have signed off.

03

Build

Five working days. Your repository from the first commit. A written update at the end of every day. You can see exactly what has been done and what is planned for the next day.

04

Handover

A recorded call walking your team through the code, the environment setup, and day-to-day operation. Then 30 days of fixes — no hourly billing, no new statement of work for bugs.

Pricing

One price. Agreed before we start.

5-Day Build

$1,500

Fixed price · USD

On agreement50% — invoice issued
On delivery50% — invoice issued

Payment by international bank transfer. Bank details are shown on the invoice — they are not included in source code or public pages.

Payment terms

  • 01An invoice is issued before each payment. You do not pay until you have a document.
  • 02First payment (50%) is due on scope sign-off, before the build begins.
  • 03Second payment (50%) is due on delivery — when the agreed scope is live and working.
  • 04If the delivered software does not do what the written scope says, you do not owe the second payment.
  • 05All quoted rates are in USD, net of local withholding and bank remittance fees.
  • 06Invoices are issued directly by LexoraTech with clear international transfer details.

Deliverables

Everything you need to run it without us.

Working software

Running on your infrastructure. Not on ours. You control the deployment from day one.

Source code

In your own repository, under your own account, from the first commit. Full history included.

Environment documentation

What env vars are needed, what services it depends on, how to run it locally and in production.

Recorded handover call

A walkthrough of the code, the setup, and day-to-day operation. Your team can watch it as many times as needed.

30 days of bug fixes

If something we built breaks within 30 days of handover, we fix it. No hourly billing, no new contract.

Daily written updates

A written update at the end of every working day during the build — what was done, what is planned tomorrow.

Scope and change policy

What the price covers. What it does not.

What “done” means

The project is complete when the agreed functionality works according to the approved written scope. Not when you are happy in general — when the specific acceptance criteria we agreed are met. If something in the scope does not work, we fix it at our cost within the 30-day period.

What “not doing what we agreed” means

The objective test is: does the agreed functionality work according to the approved scope document? If an agreed feature is materially absent, or an agreed acceptance criterion is not met, that is a defect we are obligated to fix. Subjective dissatisfaction with design, wording, or approach is not a defect — those are decisions made during scope approval.

Changes after scope approval

Any change to the agreed scope after the build begins is a new piece of work. We will quote it in writing. If it is small, it may be absorbed. If it changes the timeline, the price adjusts before we continue. We do not start work on a change until it is agreed in writing.

Delays outside our control

The five-day schedule assumes that required assets, credentials, API access, and content approvals arrive on day one. Delays caused by client-side approvals, missing content, third-party service outages, app-store review processes, hosting issues, or other external dependencies do not count as development delay on our part. If a dependency outside our control slips the timeline, we will tell you immediately and agree a revised date.

Additional features

Features not in the agreed scope are quoted separately before any work begins. There are no surprises in the other direction either — we will not invoice for anything not in the agreed scope.

Selected work

Real projects. Real deliverables.

These are actual projects Lexora Tech has built. No invented outcomes.

Inner Mental Wellness · corporate mental health

Sri Lanka’s first Employee Assistance Program platform

Workplace mental health support was fragmented. Companies had no private, central way for staff to reach a therapist — and employees would not use anything HR could see.

A platform where employees book therapy anonymously, sessions run securely in the browser, and HR only ever sees aggregated wellness reporting. Stripe handles corporate billing automatically.

Corporate clients on the platform

50+ organisations

LaravelVue.jsAWSStripeMySQL
Visit live site ↗

The Missed Lesson · national child-safety programme

The digital home of a national child-safeguarding programme

A programme run jointly by the Ministry of Education, the Police Child and Women Bureau, TEAM HERO and the ELPEC Campus was coordinating through fragmented channels and printed handouts. Staff could not publish or correct safety guidance without going back to a developer.

A deliberately lightweight PHP platform with a custom CMS, so non-technical staff publish and update safeguarding guidance themselves, in real time, with no developer in the loop.

Brief to live

12 days

PHP 8MySQLBootstrap 5jQuery

The studio

Two people. You talk to whoever is writing the code.

We’re a two-person studio. No account managers, no handoffs, no team you never meet. The person on your kickoff call is the person shipping your software.

Theekshana Sudeepa

Founder, Full-Stack Engineering

Full-stack architect on both the Inner Mental Wellness platform and the Missed Lesson system. Writes most of the backend, and would rather delete code than add it.

Praveen Lakshan

Co-founder, CTO

Runs architecture and infrastructure across the studio’s builds. Cares most about the boring parts that keep systems up at 3am.

Questions

Straightforward answers.

You’re not local — how does that work?
We work a 4-hour daily overlap with US Eastern and a full overlap with UK and European hours. You get a written update at the end of every working day, and your code sits in your repository from the first commit — not ours. In practice most clients say it feels closer than agencies in their own city, because the updates never stop.
What does a typical project cost?
The 5-Day Build is $1,500 fixed and is how most clients start. Beyond that, a focused internal tool or automation usually lands between $4,000 and $12,000. A full web or mobile application is typically $15,000 to $40,000. We quote a fixed number before we start, and we’d rather tell you the range now than waste a call.
How fast can you start?
Usually within one to two weeks. If you book a call this week we’ll tell you our real next opening on that call — we don’t hold slots we can’t honour.
Who owns the code?
You do, completely, on final payment. It lives in your repository, under your account, from day one. No licensing, no hosting lock-in, no per-seat fees to us. If you decide to take it in-house next month, everything you need is already yours.
What if it goes wrong?
The 5-Day Build is billed half up front and half on delivery. If what we ship doesn’t do what the written scope says, you don’t pay the second half. On larger projects we work in fixed-price milestones so you can stop after any one of them.
Can you work with our existing team and stack?
Yes — that’s most of our work. We join your repo, follow your conventions, and open pull requests your engineers review. If you have no engineers, we handle deployment and hosting too, and document it so you’re never dependent on us.
Can I see the code during the build?
Yes. Your repository is live from the first commit. You can see every change as it happens, follow the commit history, and leave comments. We open pull requests so you can review before merge if you prefer.
What if you cannot finish in five days?
If we are late because of something on our side, we continue until the agreed scope is done — at our cost, not yours. We do not charge extra for our own delays. The second payment is only due when the agreed scope is delivered.

Tell us what is slowing you down.

Thirty minutes. No deck, no sales script. If a 5-Day Build is not the right fit, we will say so on the call.