Skip to content
Thinqmesh

The schedule

Four weeks, week by week

The reason this is a schedule rather than an estimate is that the starting point is working software. We are not deciding how the system should work — that is settled and in production before your project begins.

What follows is the whole of it: the four weeks, the conditions the date rests on, when it does not apply, and what happens once it is over. If any of it looks like it would not survive contact with your situation, that is exactly the thing to raise on the first call.

The one that moves the date

asked in week one

Can your current system export its data? Almost every timeline that slips, slips there.

We ask before quoting, not in week three. If the answer is no, extraction becomes its own piece of work with its own date.

An illustration of a build moving through four stages from scoping to a running system.

Why we are quick

Speed comes from what is already built

Not from working longer hours, and not from cutting things out. Four reasons, and none of them is heroics.

  1. We do not start from scratch

    We already run our own HR, invoicing and training software. Yours starts from something that works. Nobody spends a month deciding how it should be built.

  2. The hard choices are already made

    Fast projects go wrong when big decisions get rushed. Here those decisions were made years ago, and they have been running ever since.

  3. A senior person owns your project

    Nobody joins your project after a short interview. They join after months of work we have checked ourselves, on these same systems.

  4. We agree what is included first

    We write down what is in and what is not before we start. Anything that could push the date, like data we cannot get out of your old system, we find in week one.

The four weeks

  1. Week 1

    Your data, in the running system

    We start from software that already works and load it with your kind of data. By the end of week one you are looking at something real, not a drawing.

  2. Week 2

    Your workflows and roles

    Who approves what, who can see what, and the rules that make it your process rather than ours. Most of the truly custom work happens here.

  3. Week 3

    Integrations and migration

    Linking up the software you already use, and moving your records across. Messy data shows up here, which is why we would rather look at it early.

  4. Week 4

    It goes live

    You start putting real work through it. Not a prototype and not a demo. A working system covering what you agreed at the start.

Conditions, not caveats

What the four weeks assumes

A fixed date only means something if both sides know what it rests on. Here are those conditions, up front, rather than discovered in week three.

  1. Scope is agreed first

    We write down what is included before we start. Adding to it later moves the date. That is normal, and far easier to handle when it was said out loud beforehand.

  2. Your data can be exported

    Moving your records assumes your current software can export them. If it cannot, getting the data out becomes its own job with its own date.

  3. Someone on your side can decide

    Four weeks needs answers in days, not fortnights. One person who can settle a question does more for the date than any amount of engineering.

Said before you ask

When it is not four weeks

Some work takes longer. Very large programmes. Jobs spanning many systems. Regulated work with audit duties. And moving data out of software that cannot export it. We say so in the first conversation, not at the end of week four.

The full detail is in our terms, which set out exactly what a four-week engagement includes and excludes.

Week five onwards

What happens after

Nothing about the four weeks locks you into anything afterwards. Here are the three things that actually happen, in order of how often.

  1. You run it, we hand it over

    A handover session and a written runbook covering deployment, backups, access and the things that will need attention. You own the code and the data. Taking it in-house is a handover, not a negotiation.

  2. The next module

    The second thing is faster than the first, because the foundation, the identity model and the deployment path are already in place. This is the common path — HR first, then invoicing, then whatever hurts next.

  3. Support, quoted separately

    If you want us to keep the lights on, that is a separate agreement with its own price. We never fold it invisibly into the build. Ending support should never feel like losing the system.

Asked and answered

Common questions

How can it be four weeks when other agencies quote months?
Because we do not start from nothing. HRKit, our invoicing system and our training platform already run here. Four weeks is what it takes to fit one of them to your business, not to invent one.
What exactly do I get at the end of four weeks?
A first working version, covering what you agreed in writing before we started. On your own system, with your data moved across, and working well enough to put real work through it.
When does four weeks not apply?
Very large programmes, work spanning many systems, regulated environments with audit duties, and moving data out of software that cannot export it. We say so in the first conversation, not at the end of week four.
What does the 10,000 rupee fee cover?
It pays for the scoping work, which produces a written scope, a delivery date and a price for the build. The written answer that comes before it is free, and the build is quoted separately.
Who actually builds it?
Senior people lead it, with a team we trained and assessed ourselves on these same systems. Because we are fitting software that already runs, the hard design decisions were settled long before your project starts.
Who owns the code and the data?
You do. It runs on your own system, the data is yours, and you get the code. We do not hold anything back to keep you. Moving to your own team or another supplier is a handover, not a negotiation.
What happens after week four?
Whatever you want. Some take it in-house straight away, with the written guide and a handover session. Others keep us on for the next piece or for support. Nothing ties you to a monthly fee, and we price support separately so you can compare it fairly.
We already have a system. Does that make it harder?
Usually it makes it easier, because how you work is already written into how the current system is set up. The one thing that really slows it down is software that cannot export its data. We check that first, because it is the most common reason a date moves.
Does the four weeks apply to AI projects too?
Yes, with one difference. Week one produces a test set and a real accuracy score on your own files, before anything is built on top. If that number says AI is the wrong tool, we say so and suggest plain software instead.
How is corporate training scheduled?
Differently. A training programme runs about eight weeks rather than four, because we measure where the team starts and report against that at the end. It is priced per team, in writing, before it begins.

Next step

Book a call

Pick a time that suits you — 30 minutes, free, no obligation. You get a straight answer on whether your idea is worth building, and if it is, a scope, a date and a number. If you would rather we rang you, leave your details instead.

Book a callAsk us to call you