New builds · existing clients and agency partners
New Laravel builds for the clients we already maintain and the agencies we work under.
We build new Laravel applications and Flutter apps, but we do not headline it. Builds go to care-plan clients whose apps we already know and to agency partners who deliver them under their own brand. Paid discovery, a fixed quote, and the care plan named in the proposal.
Internal tools from $8,000. Discovery $1,500–$2,500, credited against the build.
Discovery, build, care
Each step is priced on its own. You can stop after discovery and keep everything it produced.
Discovery
One to two weeks of working sessions. Out come the screen flow or workflow map, the data model, the integration contract and a fixed-price proposal with the care plan attached. The fee is credited against the build.
Build
Fixed price, fixed scope. Code in your repository from the first commit, a staging environment that mirrors production, tests around the paths the business depends on, and a release rehearsal before anything goes live.
Care
New software enters the upgrade calendar the day it ships. The proposal names the care plan that keeps it patched, monitored and moving, so it never becomes the legacy app someone else has to rescue.
Two floors and the discovery that sets the quote
Floors, not estimates: the fixed quote comes out of discovery and does not move afterwards.
Paid discovery
$1,500–$2,500
£1,150–£1,900 · €1,400–€2,300
1–2 weeks
Scope, screen flow, API contract and a fixed quote. Credited against the build.
- Working sessions to pin down the first release
- Screen flow or workflow map, data model and API contract
- Store-account and signing checklist for mobile work
- A fixed-price proposal with the care plan attached
Laravel internal tool
from $8,000
from £6,100 · from €7,400
3–4 weeks
One workflow taken off spreadsheets and email: roles, records, reports, and the integration it needs.
- Laravel application with authentication, roles and an admin
- One core workflow with its records, states and reports
- One integration (accounting, ERP, CRM or payments)
- Tests, staging, deployment and hand-over
- Mobile apps (see the Flutter build)
Laravel operations application
$15,000–$40,000
£11,400–£30,400 · €13,800–€36,800
6–12 weeks
Quoting, dealer ordering, stock, portals: several workflows, several roles, the systems you already run.
- Everything in the internal tool
- Customer, dealer or supplier portal with its own roles
- Multiple integrations and data pipelines
- Reporting and exports for the people who sign the invoices
Every figure, in GBP and EUR too, is on the pricing page.
What we build, and what we do not
Software that runs a business on the inside, for manufacturers, distributors and the operations teams running on spreadsheets and goodwill.
Quoting and RFQ tools
Catalogue-driven quoting with the engineering rules built in, so a quote that leaves the building is one you can honour.
Stock and order control
What is on the shelf, what is committed, what is on order — one source, with the reorder points and audit trail your accountant asks for.
Customer, dealer and supplier portals
Order status, documents, pricing and re-orders for the people outside your building, each with their own roles.
Integrations and data pipelines
Imports from messy files, exports to accounting, scheduled syncs between the systems you already run — with row-level error handling, not silent failures.
Reporting for the people who sign
Dashboards and exports built from the records the workflow already creates, not a second spreadsheet maintained by hand.
Not here
- Marketing websites and brand refreshes
- Platforms you should buy off the shelf — we will name the product
- iOS and Android apps, which have their own build page See Flutter apps.
Still on a spreadsheet? Start from the spreadsheet.
Built and documented
Laravel work written up with what we built and what changed.
Singapore-based product owner
Laravel RetainerA live Laravel product moved onto a maintained boilerplate, then carried through every Laravel major and PHP version for five and a half years, with backend feature work and server upkeep on the same retainer.
Read the case study
European owner-operated business
Laravel RetainerA CodeIgniter web application rebuilt in Laravel with its data carried across intact, then kept on supported Laravel and PHP versions and extended on request for four years.
Read the case study
German marketing-software company
Laravel RetainerNearly three years as the PHP backend developer for a marketing-software company in Germany: roadmap features, third-party API integrations, release management and server upkeep, in hours overlapping the German day.
Read the case study
Community Resource Network
Laravel RetainerA five-year Laravel relationship, still shipping: a community resource-sharing platform and the control plane behind the physical lockers it opens — signed door commands to on-site hardware, live door and temperature monitoring, alerting, and one codebase shipping as web, iOS and Android.
Read the case studyThe terms, in one list
- 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.
Start with discovery
Tell us the workflow that lives in spreadsheets and email today. Discovery turns it into a scope, a data model and a fixed quote you can take anywhere.