80% of what you pay now. For twelve months. Then it's yours.
There is no license, no seat count, and no renewal. You hire SRVCWRX as a consultant at a monthly rate set to 80% of your current field service software bill. Let's be honest about year one: while we build, you're also winding down your old contract, so that year costs more, not less. The payoff comes after — when the twelve months are up, your software cost drops to infrastructure only, and every month from then on is money back in your pocket.
What it looks like at your spend level
Plug in your team size and what you currently pay per technician. The estimate is deliberately conservative — we assume you keep paying most of your old FSM bill through the whole cutover.
See the payback on your shop
When cumulative savings turn positive.
Versus staying on your current FSM.
Conservative, after the reduced-credit election. Possible upside up to $1,204.
May qualify under IRC Section 41. Estimate only, not tax advice. Your CPA decides eligibility and files Form 6765.
How this is calculated
SRVCWRX fee is 80% of your current monthly spend for 12 months. During the cutover we assume you also keep paying your current vendor on a conservative ramp: 100% for months 1–4, 75% for months 5–10, and 40% for months 11–12. After month 12 you own the software and only pay infrastructure.
The month-13+ estimate is the midpoint of the typical infrastructure range for your spend level. Actual infrastructure costs scale with usage, not headcount.
R&D credit: 65% of contractor fees count as qualifying research spending, times the 6% startup rate under the simplified method, times 79% for the reduced-credit election (about 3.1% of fees). The upside uses the 14% rate available to companies with past research spending. When included, the credit is applied in month 12. Software built for internal use must also pass a stricter innovation test.
Month 13 figures are typical infrastructure ranges (hosting, database, email, SMS, maps) and scale with usage, not headcount. Payment processing fees are separate and go to your processor, not to software.
Your build may qualify for the R&D tax credit
The federal Credit for Increasing Research Activities rewards companies that pay to develop new or improved software. Paying SRVCWRX to build yours may count.
Why this engagement fits
- You own the results: code, data, and keys are yours.
- You pay a fixed fee whether or not an experiment works, so you carry the risk.
- The work is technical: designing, testing, and iterating on new software.
- It has a real business purpose: running your service operation.
The honest caveat
Software built for your own use faces a stricter test: it must be truly innovative, carry real technical risk, and not be something you could just buy. Some builds pass and some don't. Your CPA decides.
$16,667/mo × 12 = $200,004 in fees → × 65% qualifying × 6% rate × 79% after election ≈ $6,160 credit
About 3.1% of fees. Companies with past research spending may reach a 14% rate (possible ~$14,400 on the same fees). Startups under $5M in revenue with fewer than 5 years of revenue may apply up to $500K of the credit against payroll taxes, even with no income tax owed.
Estimate only, not tax advice. Your CPA decides eligibility and files Form 6765.
- Discovery, workflow mapping, and a written system design
- Your FSM software, built to your process and branded as your own
- Every backend account set up correctly and owned by your company
- Full data migration off your current platform, with validation
- Web app for the office plus mobile app for the field
- Hands-on training for your team on Lovable, releases, and support
- Documentation, runbooks, and a written handoff checklist
- Twelve months of iteration — this is a build, not a demo
- Third-party infrastructure costs (hosting, database, SMS, email, payments) — these are yours and typically a fraction of a SaaS seat bill
- Hardware, tablets, or phones for your crew
- Accounting or bookkeeping services
- Ongoing per-seat fees of any kind, ever
What "you own it" actually means
The code
Your repository, under your company's GitHub organization, with full history. No escrow, no license terms, no revocation.
The accounts
Every backend service — hosting, database, email, SMS, payments — is created under your company's ownership from day one.
The data
Your database, your backups, your exports. You can dump the whole thing to a file any day of the week.
The name
It isn't 'SRVCWRX software.' You name it. Your logo, your domain, your product for your crew.
The ability
Your team learns to use Lovable to change, extend, test, and deploy the software without me.
The exit
Cancel anytime — no lock-in, nothing owed for the remaining months. Paid months aren't refunded, and you keep everything delivered so far.