TradeInvoice (opens in a new tab)
Clients, estimates, jobs, and invoices in one working application.
Independent software development
ALBUQUERQUE, NM / 35.08° NSoftware and
integrations for
small businesses.
I’m Jeff. I build custom software, connect business tools, and sort out the hosting, configuration, and security that make the whole thing work.
BASED HERE.↗
Based in
Albuquerque.
CUSTOM SOFTWARE / INTEGRATIONS / TECHNICAL SUPPORT
Inquiries. Scheduling. Quotes. Payments. Customer records. The connections between them.
01 / Working software
Software
I’ve built.
Independent products I’ve designed and developed. Different problems, different kinds of software.
All 15 projects ↗
HolySheet (opens in a new tab)
A browser spreadsheet with formulas, charts, pivots, and AI explanations.
ArtistPortfolio (opens in a new tab)
Portfolio publishing, galleries, themes, and custom domains for artists.
Pinpoint Geocoder (opens in a new tab)
An address-to-coordinate API built as a standalone product.
SellThisHouse (opens in a new tab)
Tasks, deadlines, team coordination, and offer comparison for a home sale.
Cadenza (opens in a new tab)
A practice journal and repertoire library for classical pianists.
MORE PROJECTS
02 / Examples by business type
How I can help
your business.
Contractors, cleaners, electricians, plumbers, and other small businesses. Pick a trade or service to see a specific problem we could work on.
A familiar problem / 01
“The phone rings while we’re on a job. By evening, the customer has called someone else.”
Capture the request, collect the address and equipment details, and put a follow-up in the team’s existing job system. Give the office a view of inquiries that still need a response.
- 01Request + photos
- 02Office review
- 03Visit booked
- 04Quote + invoice
- Possible connections
- Jobber / Twilio / Google Calendar / QuickBooks Online
- The part to get right
- Texting consent, service-area rules, the right technician for the job, and retries that don’t create duplicate customers. An urgent request needs a clear human escalation path.
One place to see who called, what they need, and who is responding.
Read the implementation notes ↗A familiar problem / 02
“The quote is in my email. The photos are on my phone. The deposit is somewhere in accounting.”
Keep the project brief, site photos, proposal, and payment milestones together. Give customers a private place to see the schedule, approve a change, and find their documents.
- 01Project brief
- 02Site visit
- 03Signed scope
- 04Deposit + milestones
- Possible connections
- PandaDoc / Square / QuickBooks Online / Customer portal
- The part to get right
- Document versions, who can see each project, and what happens if a scope changes after signing. A signed proposal and a paid deposit are separate states.
A project history that both you and the customer can actually follow.
Read the implementation notes ↗A familiar problem / 03
“The customer approved a change by text. Now the scope, schedule, and invoice don’t agree.”
Keep the current scope, allowances, change orders, and progress payments attached to the project. Give the customer a clear approval step and show the office what is ready to bill.
- 01Scope + estimate
- 02Approved change
- 03Milestone reached
- 04Progress invoice
- Possible connections
- Existing project software / PandaDoc / QuickBooks Online / Client portal
- The part to get right
- Tie approval to a specific scope and price, preserve earlier versions, and decide who can approve changes. Separate a scheduled milestone from completed work and from a payment received.
A record of what changed, who approved it, and what should be billed.
Read the implementation notes ↗A familiar problem / 04
“A customer changes their regular clean, but the crew and reminder emails still have the old time.”
Connect recurring visits, customer changes, crew assignments, and confirmations. Give cleaners the instructions for the job they are assigned, and flag skipped or rescheduled visits before billing.
- 01Property intake
- 02Recurring schedule
- 03Crew + visit
- 04Invoice + follow-up
- Possible connections
- Jobber or existing scheduling software / Calendar / Email or SMS / Accounting
- The part to get right
- Recurring exceptions, travel buffers, staff availability, and billing rules for skipped visits. Access codes and property instructions need restricted visibility; they should not appear in general reminder messages.
The customer, crew, and office work from the same visit details.
Read the implementation notes ↗A familiar problem / 05
“I can’t estimate the job yet. I’m still chasing panel photos, site details, and what the customer actually wants.”
Build intake around the job type—an EV charger, panel upgrade, lighting, or a service call. Gather useful photos and questions, prepare a summary for the electrician, and track site visits and estimate approval.
- 01Job-specific intake
- 02Electrician review
- 03Site visit + quote
- 04Approval + scheduling
- Possible connections
- Custom forms / Jobber or existing job software / Calendar / QuickBooks Online
- The part to get right
- Photos support a qualified person’s assessment; they do not establish load capacity, code compliance, or safety. Mark missing information, keep final pricing under review, and record permit or inspection steps where needed.
Better information before the visit and a clear path from assessment to approved work.
Read the implementation notes ↗A familiar problem / 06
“The leak call, tomorrow’s installation, and the estimate request all land in the same inbox.”
Separate urgent service requests from planned work, capture location and the customer’s description, and route them to the office. Track technician assignment, estimate approval, and the invoice after the visit.
- 01Request + location
- 02Human triage
- 03Assign + approve
- 04Complete + invoice
- Possible connections
- Jobber or existing dispatch software / Twilio / Calendar / Payments
- The part to get right
- Define what happens when nobody is available. An automated acknowledgment must not imply a technician is dispatched. Keep emergency decisions with a person and account for service areas and changing job duration.
An office queue that separates urgent calls, booked jobs, and estimates needing attention.
Read the implementation notes ↗A familiar problem / 07
“We keep stopping work to ask for approval or explain where the repair stands.”
Add an intake flow for the vehicle and problem, collect photos and notes, and give customers a clear estimate-approval step. Put approved work and status updates in front of the office.
- 01Vehicle intake
- 02Inspection notes
- 03Customer approval
- 04Pickup + payment
- Possible connections
- Existing shop software / Email or SMS / Payments / Accounting
- The part to get right
- Confirm the shop system’s API access first. Keep the approval attached to the exact estimate version, record authorization, and leave diagnosis and safety decisions with the technician.
A visible record of what was proposed, approved, and communicated.
Read the implementation notes ↗A familiar problem / 08
“Online booking works—until someone picks the wrong service, cancels, or needs two staff members.”
Configure booking around the actual service: duration, staff, resources, preparation questions, and any deposit. Connect changes to reminders so customers don’t get messages for canceled visits.
- 01Choose service
- 02Match availability
- 03Book + deposit
- 04Remind + rebook
- Possible connections
- Square Appointments / Google Calendar / Email / MailerLite
- The part to get right
- Resource conflicts, time zones, refund rules, and a recovery path when payment succeeds but booking fails. Newsletter signup stays separate from appointment messages.
A booking process that reflects the way the studio runs.
Read the implementation notes ↗A familiar problem / 09
“Every new client means another round of chasing documents, access, and unanswered questions.”
Create a structured onboarding checklist, a private upload area, and a view of what’s still missing. Prepare follow-up drafts and keep engagement documents and meeting details attached to the client.
- 01Client intake
- 02Secure upload
- 03Review + follow-up
- 04Ready to work
- Possible connections
- Google Workspace or Microsoft 365 / Dropbox Sign / Client portal
- The part to get right
- Client-by-client permissions, document retention, expiring links, and account handover. Decide explicitly which information can be processed by AI; sensitive documents don’t need to go through a model.
Less searching through email to find out whether a client is ready.
Read the implementation notes ↗A familiar problem / 10
“My portfolio gets interest, but custom orders disappear into DMs and spreadsheets.”
Turn a commission inquiry into a clear brief with dimensions, references, budget, and timing. Track the agreed scope, deposit, progress updates, and final balance alongside a portfolio that shows the work well.
- 01Commission brief
- 02Scope + estimate
- 03Deposit
- 04Updates + delivery
- Possible connections
- Portfolio site / Stripe or Square / Email / Google Sheets
- The part to get right
- Availability and edition counts, changes to custom orders, image upload limits, and clear shipping or pickup expectations. Keep sales records consistent with the tools the shop already uses.
An organized path from “I love your work” to a finished order.
Read the implementation notes ↗Illustrative projects, not client case studies. We confirm the tools, access, and scope for your business.
Showing HVAC companies03 / Beyond the first version
Development,
configuration,
and support.
A good prototype gives us something to work with. Putting it into daily use means answering the less visible questions, too.
Read the technical integration guide ↗APIs / data / recovery
Connect the systems.
Map the records, choose which app owns the data, and handle failed syncs. A payment should update the right invoice—even when the notification arrives twice.
Hosting / cost / deployment
Choose the right hosting.
Decide what needs a server, what can stay static, and which managed services are worth paying for. Set up domains, environments, backups, and a way to roll back a bad release.
Accounts / DNS / configuration
Get the configuration right.
Connect accounts with the right permissions. Configure email delivery, calendars, payment settings, and secrets. Document the setup so it doesn’t depend on someone remembering what they clicked.
Access / validation / security
Set up access and security.
Make sure a customer can only open their own documents. Validate uploads and requests, limit access, and keep credentials out of the browser. Test permissions with more than one account.
Usability / accessibility / testing
Make it easy to use.
Clear forms, readable screens, keyboard access, and useful errors. Test on a phone, with missing information, and with the people who will actually use it.
04 / How I work
Work directly
with me.
JEFF SANCHEZ / HIGH DESERT APPS
Tell me what you use now and what you’d like to improve.
I use AI to write and explore software faster. I’m still responsible for understanding the problem, reviewing the code, testing the behavior, and making the technical decisions. Those are part of the job.
We start with your current setup. Sometimes the fix is configuration. Sometimes it’s a connection between two tools. Sometimes a small custom app is the right answer. You’ll get a defined scope, costs, and a way to tell whether it’s working.
You should own your accounts and know how the system is put together. I’ll document the setup, walk you through it, and agree on what ongoing support includes.
Understand the workBuild a useful versionTest it with you
A few practical questions
Can you work with the tools I already have?
That’s the starting point. I’ll check the exact products, plans, and available integrations before proposing a change. A tool that already solves the problem is worth keeping.
What if I’ve already built something with AI?
Bring it. I can assess the code and setup, explain what is ready to use, and scope the work needed around data, permissions, hosting, reliability, and usability.
Can we start with one small thing?
Yes. One awkward handoff or repeated task can be a useful first project. We agree on what’s included, the price, and any software subscriptions before work starts.
Do you work outside Albuquerque?
Yes. I’m based in Albuquerque and interested in working with local businesses, including Rio Rancho and Corrales. We can also work remotely.
Have a question or a project in mind?
What can I
help you with?
Need help setting up software, connecting your tools, or building something? Send me a short message.
Contact Jeff
Local to Albuquerque. Happy to talk through a remote project, too.