Start with the work the software supports.
Existing software carries more than code. It may hold years of customer records, produce a report someone needs every Monday, or contain rules that only become visible when an unusual job comes in. Even a frustrating system may be doing several important things correctly.
We begin by learning where the system sits in the business. Who uses it? Which decisions depend on its data? What happens when it is slow or unavailable? Where do people leave the system for a spreadsheet, email, or handwritten note? Those questions help separate a software defect from a process problem and a missing capability. We also look ahead: what changes are planned for the business, and what will your team need from this system? We weigh recommendations against those needs as well as today's problems.
That context matters when responsibility for the system has changed. Perhaps the original developer is no longer available. An internal team may understand the business but have little room for another queue of fixes. Or the software may work well enough that nobody wants to disturb it, even as the workarounds around it keep growing. We can meet the system where it is and build a shared understanding before changing it.
Make changes in useful, reviewable pieces.
Once we understand the dependencies, we can narrow the work. A first change might make an unreliable report trustworthy, remove a repeated entry step, improve a difficult handoff, or document an area that has become risky to touch. The right starting point is the smallest piece that makes the working day meaningfully better and teaches us something about the system.
We make the reasoning visible as the work moves. Your team should be able to see what we learned, which assumptions shaped a change, and what still needs to be checked. Working software gives the people who use it something concrete to review. That is especially useful when an internal developer or technical lead needs to remain part of the decision.
Midwestern Engineers' planning work used the production assignments already held in its business system. The same assignments could be viewed by project, team, or engineer, with dates and the latest note kept together. Its IT manager reported better coordination and timeline monitoring across the business.
Read how the Midwestern planning view worked.
See how we learn the work before changing it
Sometimes keeping everything creates more work.
Connecting tools can sound safer than replacing them, but a growing chain of connections can leave staff maintaining the same information in several places. If the core system no longer gives the team a dependable record, preserving every part of it may protect the problem instead of the business.
At Oasis, staff already had a process. We brought the work they were carrying between spreadsheets, documents, and people into a shared office system. QuickBooks continued to handle accounting, with contract preparation, signing, and payment requests connected to the job.
What has the customer actually agreed to?
Old estimates and later changes leave staff piecing together what was agreed. Here, the office can see the current pool agreement and its approved addition, separate from a driveway quote that has not been accepted.
Reception was rebuilding the paperwork for each job.
Checking flood zones and preparing contract fields was repeated work for reception. We put the job’s location and type into the preparation rules. The original $110,000 scope and payment terms carry through for staff to review.
The next person needs the news to act.
Staff previously checked signatures and marked them by hand. Now signing prompts the PM’s notice and the customer’s $40,000 deposit request. The handoff can happen without another manual check; the request is still unpaid.
What is still owed, and what changed?
Accounts needs to distinguish money received from an unpaid request and include approved additions. Here, a signed $5,000 change brings the agreement to $115,000. With $40,000 received, $75,000 remains across the payment milestones.
Harborview 1042
PM Jamie ExamplePool + Spa Paver Driveway
Property & peopleJamie Example · St. Petersburg · Flood zone AE
Primary contact
Example Design Studio
Business · receives communications
HomeownerAlex Example
Location
- Job site
- 1042 Example Lane
St. Petersburg, FL - Municipality
- St. Petersburg
- Zone
- South
- Flood zone
- AE
Unclear lookup results require review.
Connected records
Estimates, contracts, changes and payments belong to their job.
QuickBooks handles accounting. Signing is connected to the office workflow.
Overview · jobs and current work
Keep the driveway quote separate from the pool and spa work.
Jamie ExampleSales · jobs on this property
Two separate scopesPool + Spa
$115,000with signed change| Record | Status | Amount |
|---|---|---|
| EstimateEST-2026-0042 | Contracted | $110,000 |
| Current contractCON-2026-0101 | Active | $110,000 |
| Signed change orderCO-0001Extend the deck by 120 sq ft | Signed | +$5,000 |
3 earlier versions
| EstimateEST-2026-0038 | Superseded | $104,400 |
| ContractCON-2026-0099 | Superseded | $105,200 |
| Change orderCO-0009 | Signed | $2,400 |
CO-0009 belongs to the replaced contract, not the current agreement.
The coping payment is requested. Follow up with the homeowner.
Paver DrivewayEstimate sent · $9,400
EST-2026-0051 · Separate job, awaiting customer feedback.
Paver Driveway
$9,400| EstimateEST-2026-0051 | Sent | $9,400 |
Awaiting feedback. This job has not reached a contract.
The contract built from the estimate
Staff choose Save to contract
The estimate becomes the agreement.
Scope, price and payment terms carry across. Staff review the draft before sending it.
CON-2026-0101
Harborview 1042
Pool + Spa
Exhibit A · scope and price
Pool and spa scope. The driveway remains a separate estimate.
Sections, quantities and prices carry from the prepared estimate.Payment terms carried from the estimate
- At contract signing
- $40,000
- Coping installed
- $40,000
- At completion
- $30,000
Document selection follows this job
Stored rules select the matching documents. Staff can review or change that selection.
Review the assembled contract and choose when to send it.
This view explains the original $110,000 agreement. The later signed deck change is kept in its own record.
What follows a signed contract
When the customer signs
The signature starts the next handoff.
Before, someone checked the signing service, marked the record and carried the news to the office.
CON-2026-0101
Payment schedule created
| Down payment | $40,000 | Requested |
| Coping installed | $40,000 | Unpaid |
| Final balance | $30,000 | Unpaid |
The next people are notified
CON-2026-0101 · linked to the job
Payment link for the first milestone
Choose a payment method and pay. No payment has been recorded at this point.
The request requires a valid recipient and billing setup. A request, its invoice and a confirmed payment remain separate records.
Payment schedule and recorded money
A payment is recorded or matched from QuickBooks
The money and the job stay in step.
This later view includes the signed $5,000 deck extension.
Payment terms
Current agreement| Payment term | Amount due | Paid | Status |
|---|---|---|---|
| Down paymentAt contract signing | $40,000 | $40,000 | Paid |
| Progress paymentCoping installed | $40,000 | $0 | Payment requested |
| Final balanceAt completion | $35,000 | $0 | Unpaid |
| Contract | $110,000 | ||
| Signed change order | $5,000 | ||
- Total
- $115,000
- Received
- $40,000
- Remaining
- $75,000
The milestone balance updates, a receipt goes to the customer, and the PM gets the notice.
The later coping payment is requested, not paid. Follow up on that milestone.
Staff record payments or the system matches QuickBooks records. Unclear matches and failed communications still need review.
Files connected to the job
Files for Harborview 1042
The supporting material stays with the job.
- PDFCON-2026-0101.pdf
Pool + Spa · contract
- JPGpool-tile-choice.jpg
Pool + Spa · material selection
- PDFpaver-spec.pdf
Paver Driveway · product information
Activity for this property
Activity
The next person can see what happened.
- PMPrepared the Pool + Spa estimate
EST-2026-0042 · $110,000
- SystemRecorded the signed contract
CON-2026-0101 · payment schedule created
- SystemRecorded the $40,000 deposit
Pool + Spa · customer receipt and PM notice
- PMAdded the signed deck extension
CO-0001 · +$5,000
Communication history
Communications
The message belongs to the job.
Deposit received — PMCON-2026-0101 · To: pm@example.comSent
Deposit received · CON-2026-0101
The $40,000 deposit is recorded against the Pool + Spa contract.
Contract signed — PMCON-2026-0101 · To: pm@example.comSent
The Pool + Spa contract has been signed. Its first payment request can follow.
Replacing a specific part can be the more conservative decision when it removes repeated entry, unclear ownership, or a dependency nobody can safely maintain. We will say so when the evidence points there. We will also say when a repair, a new view, or better documentation is enough.
Ongoing help should match the responsibility.
Some systems need a dependable owner more than a large project. That can mean monitoring, alerts, patches, security updates, current documentation, and a direct path to an engineer when something goes wrong. Other teams have a continuing queue of features, reports, and connections that needs regular planning. A business with broader technical decisions may also need leadership around vendors, contracts, budgets, and the development calendar.
Care, Team, and Advisory describe those different levels of ongoing responsibility and usually follow a build. For an existing system, we first need to understand its condition and what taking responsibility for it involves. That helps us decide what work is needed before an ongoing relationship fits; it does not mean a new build is required. The pricing page explains the packages and their starting prices.