- Articles
- 25
- Category
- Technology
- 26 September 2026Household permissions for pet booking portalsSeparate booking, payment, pet information and pickup permissions instead of assuming everyone linked to a household has the same authority.
- 26 September 2026Pet service packages with an explainable session balanceTrack prepaid entitlements through bookings, attendance, cancellations and corrections without treating one editable balance as the entire record.
- 26 September 2026Recurring dog walks with exceptions that do not duplicateSeparate a standing walking arrangement from each visit so holidays, cover and one-off changes do not corrupt the next week of work.
- 26 September 2026Grooming schedules that learn from the work recordUse reviewed service history and explicit resource rules to estimate grooming appointments without treating breed alone as a reliable duration.
- 26 September 2026Boarding capacity is more than a count of kennelsRepresent suitable spaces, overlapping stays, household sharing and review requirements before confirming a boarding reservation.
- 26 September 2026Reviewed cleaning hours from rota to payroll exportKeep planned shifts, attendance events, approved hours and exported records distinct so corrections remain traceable across the payroll handoff.
- 26 September 2026Site consumables replenishment without duplicate ordersConnect site counts, approved replenishment and delivery receipts while keeping requested, ordered and available stock separate.
- 26 September 2026Client cleaning reports that explain exceptionsBuild a client portal around completed work, unresolved exceptions and follow up actions instead of a wall of green checkmarks.
- 26 September 2026Cleaning cover swaps that preserve site access rulesA replacement cleaner needs more than an empty shift. Model eligibility, access instructions, acceptance and handover as part of cover scheduling.
- 26 September 2026Cleaning attendance exceptions without false proofUse check-in signals to find uncovered shifts while recognising the limits of location, shared devices and site codes.
- 26 September 2026Turning a cleaning contract into versioned site checklistsTranslate a site scope into daily and periodic work without losing the agreement behind each task or rewriting the history of completed visits.
- 26 September 2026Arrival windows that do not promise an impossible dayOffer home-service appointment windows from real capacity, then keep confirmation, estimates and changes distinct in the customer experience.
- 26 September 2026Van stock and return visits need one parts workflowConnect part requests, reservations, van transfers and job consumption so a return visit is scheduled against more than an expected delivery date.
- 26 September 2026Equipment history that survives a technician changeConnect sites, installed equipment and service visits without turning every note into an unsearchable customer timeline.
- 26 September 2026A dispatch board that understands the job, not just the calendarModel skills, travel, parts and job state before letting a dispatch board assign technicians. A free rectangle is not proof that a visit is feasible.
- 21 September 2026Retrieval over your own documents: what decides qualityMost retrieval systems fail on chunking, metadata and permissions rather than on the model. What to get right before choosing anything else.
- 15 September 2026Idempotency: the idea that prevents duplicate everythingA lost response can turn a reasonable retry into a duplicate order, email or charge. Idempotency helps, but its boundary must include the actual effect.
- 11 September 2026Why your spreadsheet is the most valuable document in the businessThe file one person maintains usually contains rules nobody has written down. Extracting them is the highest value part of a modernization project.
- 9 September 2026Deciding which system owns which fieldA sync cannot resolve conflicting business rules on its own. Decide who can write each field before connecting the systems.
- 8 September 2026Dead letter queues, and why silence is the worst failureA failed integration needs a visible recovery path. Retry budgets, failed work queues and reconciliation prevent errors from disappearing into logs.
- 7 September 2026Integrating with a system that has no APIExports, database replicas and file exchange are all workable. Screen scraping usually is not, and here is how to tell the difference.
- 4 September 2026Testing what matters rather than chasing coverageA coverage percentage tells you almost nothing. Ranking behaviour by what a failure would cost tells you where to spend.
- 2 September 2026Performance budgets, and why averages lieA page that is fast on a development machine with fifty records tells you nothing. Set the budget first and measure against real conditions.
- 29 August 2026Why the database should refuse invalid dataApplication validation holds only for the paths someone remembered. A constraint holds for every path, including the import script written at midnight.
- 23 August 2026Reconciliation: the job that runs when nothing is wrongScheduled comparisons can find missing or inconsistent records even when no request reported an error.
Let’s talk about the system you need.
Tell us where the current process breaks down. We can map the workflow, examine the integration requirements and define a practical scope for the build.
- A mutual NDA is signed before project details are shared.
- Scope is fixed in writing before any build starts.
- You own the source code, the IP and the documentation at delivery.
- Support plans are available and tailored on a discovery or technical call.