Terms of Service
Last updated: 15 October 2026
The Short Version
These terms exist to protect both of us. We believe in fairness, transparency, and treating you the way we'd want to be treated.
- Scope and a fixed price are agreed in writing before work begins
- Half up front, half on hand-over; care plans invoiced monthly
- You own the code, in your repository, from the first commit
- Either party can end the engagement fairly
That's the gist. Keep reading for the details, or reach out if you have questions.
What We Do
JIGOMIT keeps the Laravel applications businesses run on upgraded, secure and moving, and builds the operations software around them.
Our services include:
- Fixed-price Laravel upgrades and rescues
- Monthly care plans with a response-time SLA, with a Mobile module for the Flutter app that talks to the application
- Store-compliance upgrades for Flutter apps on a Laravel backend
- New Laravel applications and Flutter apps on a Laravel API, built at a fixed price after paid discovery
- Custom operations software built on Laravel and Vue
- White-label Laravel and Vue development for agencies
Every project is different. We'll discuss your specific needs and agree on the scope before any work begins.
How We Work Together
We offer different ways to work together, depending on your needs:
Fixed-Price Packages
Upgrades, rescues and scoped software builds
- Scope and price agreed in writing before work starts
- Fixed means fixed: a misestimate is our cost
- Half invoiced up front, half on hand-over
- New requests are quoted separately, never added silently
Care Plans
Ongoing maintenance with a named engineer
- A block of engineering hours a month with a written SLA
- Three-month minimum, then month to month
- Unused hours do not roll over
- A month of notice to stop, with everything already in your repository
Agency Partnerships
Fixed-price sprints under the agency’s brand
- NDA and non-solicitation agreed before any client is named
- Named engineers, stated in the agreement
- The same fixed-price terms as direct clients
- Hand-over notes delivered with every sprint
Payments & Fees
We believe in transparent pricing. Here's how payments work:
- The price is agreed in writing before work begins and does not move
- Fixed-price work: half up front, half on hand-over
- Care plans: invoiced monthly in advance, three-month minimum
- We invoice in USD unless agreed otherwise; bank transfer and card accepted
- Scope changes are quoted separately and approved before they start
If you're ever unsatisfied, let us know. We'll work with you in good faith to make things right.
Revisions & Changes
Getting things right matters. Revisions are a normal part of how we work:
- Revisions are a normal part of the process
- Scope changes are discussed before we continue
- We communicate clearly at every step
- Additional requests are quoted separately
We don't nickel-and-dime you. If something needs tweaking within the agreed scope, we'll take care of it.
Working Together
Great projects are a partnership. Here's what helps us do our best work for you:
Provide timely feedback on our work
Share content and assets when needed
Respond to questions within a reasonable time
Be available for key decisions
We know you're busy. We just ask for reasonable responsiveness so we can keep things moving.
Timeline & Delivery
We move fast, but never at the expense of quality:
- Each package states its duration; custom work states it in the scope document
- Anything that threatens the date is raised the day we see it, with options
- Production releases happen in a window you choose, after a staging rehearsal
- Care-plan response times are the ones written in your plan
Ending an Engagement
Sometimes things don't work out. That's okay. We handle cancellations fairly:
- Fixed-price work: either party can stop; completed work is paid for and already in your repository
- Care plans: after the three-month minimum, a month of notice from either side
- Hand-over notes are delivered whenever an engagement ends, however it ends
- No penalties for good-faith cancellations
We want you to be happy. If you need to stop, we'll make the transition as smooth as possible.
Mobile App and Store Work
Work inside the App Store and Google Play carries liability a Laravel engagement never had, so these clauses apply to every mobile upgrade, Flutter build and Mobile module, in addition to everything above.
- 1
You own the store accounts
You enrol as an organisation and remain Account Holder on Apple and Owner on Google Play, and you pay Apple and Google directly. We never submit your app under our own account.
- 2
Least-privilege access
On Apple we work as App Manager with Certificates, Identifiers & Profiles access, and as Admin only when a team API key must be created, documented each time. On Google Play we hold app-level release and testing permissions, never Owner. Access is revoked within five working days of offboarding.
- 3
Keys and certificates stay in your custody
Distribution certificates and profiles are kept in a repository or bucket you own. API keys are scoped to App Manager. Apple allows one distribution certificate per team and lets a key be downloaded once; we hand you a rotation runbook at onboarding.
- 4
Android signing
Android releases use Play App Signing with the upload key in your custody. We hold no app signing key.
- 5
SLA carve-outs
Our response times cover our work. Store review time — Apple typically under 48 hours for nine in ten submissions, Google up to seven days or longer — the 12-tester, 14-day gate on new personal Play accounts, and developer-verification holds are outside the clock.
- 6
What compliance covers
Store-rule changes that need toolchain, SDK or metadata work — target API, Xcode floor, privacy manifests, age ratings, trader status, 16 KB pages — are inside the Mobile module. Rejections on content, legal, business-model or design grounds are quoted separately.
- 7
No backlog in the module
An app more than one sprint behind joins the Mobile module only after a paid Store-Compliance Sprint or Catch-up Upgrade.
- 8
Device testing
Firebase Test Lab free tiers and one physical device per platform are included. A wider device matrix is passed through at cost.
- 9
Removals you declined to prevent
We are not liable for removals under Apple's inactive-app rule or Google's policy enforcement where you declined the scheduled compliance work in writing.
- 10
Liability cap
Our liability on store work is capped at the fees paid in the preceding three months, because a broken signing setup can block every release, not one feature.
Who Owns What
Let's be clear about ownership:
- You own the code we write for you; it lives in your repository from the first commit
- You retain ownership of all data and content you provide
- We may describe the work anonymously in case studies unless you ask us not to
- Open-source packages retain their own licences
In short: once you pay, it's yours. We just ask to show it off in our portfolio unless you'd prefer we don't.
Liability & Expectations
We take our work seriously, but here are some reasonable limits:
- We work in good faith and rehearse every release on staging first
- We fix defects in work we delivered, inside the scope, at no charge
- Our liability is limited to the amount you paid us for the engagement
- We cannot guarantee the behaviour of third-party services or hosting we do not control
We're not trying to dodge responsibility. We just want to set fair expectations for both sides.
Changes & Questions
We may update these terms from time to time. When we make significant changes, we'll let you know if we have your contact information.
Have questions about anything here? We're happy to explain. Just reach out:
We believe in transparency. If something isn't clear, just ask.