"Thirty-something thousand dollars for a web page and some text messages" is a fair thing to balk at. So here is every day of work inside that number, what actually drives the range, and three honest ways to pay a lot less than it.
Not a website. A scheduling system that takes messages in, routes work to the right person, tracks whether they answered, and keeps the money straight. Every line below is something that has to exist before the thing is usable on a Tuesday morning.
| What gets built | Why it exists | Days |
|---|---|---|
| Accounts and permissions | You, a coordinator later, different access | 3 |
| Database and data model | Members, properties, jobs, vendors, fees | 3 |
| Inbound texts become records | A member's text turns into a tracked request, threaded to them | 5 |
| Dispatch board | Everything open, with the response clock running | 5 |
| Contractor bench | Vendors, documents, and automatic suspension when insurance lapses | 4 |
| Offer engine | Send an offer by text, parse the reply, expire it, re-route to the next vendor | 6 |
| Quote review | Log it, compare against past jobs, approve or send back | 4 |
| Scheduling and close-out | Book a window, record what was actually invoiced | 3 |
| Fee ledger | Accrue 10%, invoice it, chase it, reconcile it | 4 |
| Member and property records | The home file — roof age, HVAC age, repair history | 3 |
| Maintenance reminders | Nightly job that finds what is coming due and texts about it | 3 |
| Photos in and out | Picture messages, stored against the job | 2 |
| Stripe sync | Who is actually a paying member right now | 2 |
| Carrier registration | Business texting has to be registered or it gets silently filtered | 2 |
| Testing and fixing | Roughly a fifth of any build that you intend to trust | 8 |
| Deploy, monitoring, handover | Live, watched, and documented enough that someone else can take it over | 3 |
| Total | One developer, about twelve weeks | 60 |
Sixty days is sixty days. What moves the number by a factor of three is the hourly rate of the person doing them. This is the single most useful thing to understand before you take quotes from anybody.
| Who builds it | Rate | This scope | What you are trading |
|---|---|---|---|
| Offshore agency | $50–70 | $24k–34k | Cheapest. Timezone gap, and quality varies enormously between shops |
| Senior contractor, AI-assisted | $70–110 | $34k–53k | One accountable person who can move fast. Bus factor of one |
| US agency | $125–175 | $60k–84k | Project management, continuity, someone to sue. You pay for all three |
The proposal originally said $25k–40k for this. Working it out line by line, that was low — it only holds at the cheapest end of the offshore range. The honest figure for a senior contractor is $35k–50k, and I would rather tell you that now than discover it in month three.
All of them are real options. I would take any of them over spending $40,000 before you know the business works.
Inbound texts become tracked requests, offers go out by text, replies get parsed, unanswered offers expire and re-route to the next vendor on the bench. A minimal board to watch it happen. Nothing else.
Airtable for the data, Softr or Glide for the board, Make or Zapier to wire the automation, Twilio for the texting. A working system in two or three weeks.
Jobber for dispatch, OpenPhone for texting, a spreadsheet for the bench. What you are launching on anyway.
At 350 members this business does roughly $116,000 a year. Spending $40,000 of it on software before you have the members is not a technology decision, it is a solvency decision. Every option on this page exists so you do not have to make it.