For agencies
A senior Laravel and Vue pair your clients will think is yours.
Fixed-price sprints delivered under your brand, by two named engineers who stay on the account. NDA and non-solicitation before any client is mentioned. Hours that overlap the UK and EU day in full.
What you are buying
A named senior pair
Two engineers you meet before the first sprint, named in the agreement, and the same two on every sprint after. One leads Laravel, one leads Vue; both read each other’s code.
Your brand, not ours
We work in your repositories, your project tools and your meeting rooms, under your email domain if you want. Our name appears nowhere your client can see.
NDA and non-solicitation as standard
Both are in the partner agreement before any client is named. We will not approach your clients during the engagement or for two years after it.
Fixed-price sprints
Each sprint has a one-page scope and a fixed price you can mark up with confidence. If we underestimated, the overrun is ours.
The two ways white-label goes wrong
Every agency that has outsourced development has a story about one of these. The agreement is designed around both.
Junior substitution
The failure
The senior you met sells the work; a junior you never met does it. Quality drifts, your client notices, your reputation carries the cost.
How we design against it
The two engineers are named in the agreement. Nobody else commits to your repositories. If one of the pair is unavailable for more than a week, you are told before it happens and may pause the sprint without penalty.
Going dark
The failure
Replies slow down, then stop, usually in the week your client is asking for a demo.
How we design against it
A written reply inside one UK business day is in the agreement, every sprint has a mid-point check-in on the calendar before it starts, and you can see the branch moving in your own repository every day. Our working hours overlap yours in full.
How hand-over works
- Every sprint ends with a written hand-over: what changed, why, and what we left alone
- Pull requests small enough for your team to review, with the reasoning in the description
- Tests passing and a deploy rehearsed on staging before we call anything done
- Documentation lives in your repository, so your team owns it when the sprint ends
How change control works
- Scope is fixed once the sprint starts; new requests go onto the next sprint’s list
- Anything that threatens the fixed date is raised the day we see it, with options
- You decide whether a change is in or out; we price it, not argue it
Start with a pilot sprint
One fixed-price sprint on a real piece of client work, with the full hand-over, under your brand. You judge the code, the communication and the invoice before anything longer is discussed. If it is not right, you keep the work and we part without a further conversation.
A pilot is priced as an Upgrade Sprint — $2,500 (£1,900 · €2,300), 7–10 working days — or scoped to the client work you bring, at a fixed price agreed before it starts.
Propose a pilot sprintOur published packages
Upgrade Sprint
$2,500 · 7–10 working days
Full Upgrade
$4,500–$6,000 · 2–3 weeks
Mark up as you see fit; our prices are the same direct or through you.
How the commercial side works
Four things agencies ask before the first call, answered before it.
The client stays yours
The contract, the invoice and the relationship sit with your agency. We never hold a direct agreement with your client and never ask for one.
Resell the care plan under your brand
Our monthly care plans can be sold on as your own maintenance offer at the price you choose. We deliver the hours and the response time; the client sees your name on the report.
No exclusivity, no minimum
Bring one project or ten. We do not ask you to route all Laravel work through us, and there is no retainer to keep a bench warm.
Same prices direct or through you
The fixed prices published on this site are what you pay. Your margin is the difference between that and what you charge, and we do not undercut it by quoting your client.
Questions agencies ask
Will your name appear anywhere?
No. Not in commits, not in documentation, not on calls with your client unless you introduce us as part of your team. The partner agreement puts that in writing.
Can we start with something small?
Yes — the pilot sprint exists for that. One fixed-price sprint on a real piece of client work, with the full hand-over, so you can judge the code and the communication before committing to anything longer.
How do you handle our client asking who you are?
However you have briefed us. Most partners introduce us as their senior engineers, which is accurate for the duration of the engagement. We never contradict that and never hand out our own contact details.
Can we resell the care plan under our brand?
Yes. You set the client price and own the agreement; we deliver the engineer-hours, the patching and the response time inside the SLA, and the monthly report carries your name. The one thing we ask is that the app has passed an upgrade or audit first, so the plan starts from a known state.
We are a Dutch or Irish agency. Does that change anything?
No. We work in English, our hours cover your full working day, and the same fixed prices and agreement apply. Most of our partner conversations start on LinkedIn or through your contact form rather than by email, and we are happy with either.
What stacks do you cover?
Laravel on the back end, Vue and Inertia on the front end, MySQL or PostgreSQL, Redis and queues, and the hosting around it. If a project is mainly something else, we will say so rather than learn on your client’s budget.
Terms that apply to every sprint
- Half of the fixed price up front, half on hand-over. No surprises in between.
- Fixed means fixed: if we underestimated, that is our cost, not yours.
- You own every line. Code lives in your repository from day one.
- Care plans run month to month after a three-month minimum.
- Working hours overlap the UK and EU day in full; the US East Coast morning in part.
What you are actually buying
The answer to "why an agency in India?", in writing.
Who you contract with
Jigomit LLP, Ahmedabad, India. The company name on the contract and on every invoice.
UK/EU working hours
Working hours overlap the UK and EU day in full; the US East Coast morning in part.
NDA before requirements
We sign your NDA, or send ours, before you share a repository or a brief.
You own every line
You own every line. Code lives in your repository from day one. All IP in the work transfers to you on payment.
Named engineer
The same engineer stays on your account. No junior substitution.
Fixed means fixed
Fixed means fixed: if we underestimated, that is our cost, not yours.
Data-processing terms published
UK GDPR Article 28 processing terms are published and signed as a schedule to the engagement letter. Read the data-processing terms
Written SLAs
Response times in the contract, not on a slide.
Bring us the project you are nervous about
Tell us the stack, the deadline and what the client has been promised. We will say whether we are the right pair for it, and what the pilot would cost.
Propose a pilot sprint