Waller Creek Software provides software maintenance and support in Austin for the systems we build and for custom software already running your operations. The work falls into three jobs: keep it running, keep it safe, and keep it useful. You talk directly with co-founders Taylor Moses and Jamison Dyal, and you keep ownership of the code and data the whole time.
Job one: keep it running
Most problems give a warning before users notice. A slow query starts taking longer, an integration retries more often, a storage limit creeps closer. We watch for those signals with monitoring and alerts, and we fix what we find before it turns into a call from your front desk or your plant manager.
When something does break, you get a clear path to us and a plain explanation afterward: what happened, what we fixed and what we changed so it does not happen again. For Austin businesses that run patient visits, production lines or sales calls on their software, that steady attention is the core of software maintenance and support.
- Uptime and error monitoring with alerts
- Integration health checks and replay of failed messages
- Bug fixes with a written note on the cause
- Performance tuning as your data grows
Job two: keep it safe
Security is never a one-time setting. Frameworks, libraries and servers publish fixes all the time, and the ones left unapplied are how many breaches start. We apply updates and patches, test them in a staging copy first, and keep a record of what changed and when.
We also handle the safeguards nobody thinks about until they matter: encryption, multi-factor authentication, role-based access, backups that are proven by actually restoring them, and periodic reviews of who still has access. When an employee leaves, their access should leave with them. Good software maintenance and support makes that a habit instead of a scramble.
- 1 Monitor
- 2 Spot an issue
- 3 Fix and test
- 4 Release
- 5 Report back
Job three: keep it useful
The best ideas for your software arrive after people use it every day. A nurse wants one more field on the intake form. A shop supervisor wants the quality report sorted by line. A sales manager wants a leaderboard on the rep dashboard. These are small requests, and they are the difference between a system people like and one they tolerate.
We keep a running list of these requests with you, help you decide which ones are worth doing, and ship them in small, tested releases. This is the Optimize step of our process (Discover, Design, Build, Launch, Optimize), and it is where software maintenance and support turns into steady improvement for Austin teams.
✕Problems discovered when a customer complains
✓Monitoring flags problems before users notice
✕Security patches pile up unapplied
✓Updates tested and applied with a written record
✕Former employees still have system access
✓Access reviewed and removed when people leave
✕Small requests wait behind big projects
✓Small improvements shipped in tested releases
✕Nobody knows what changed or why
✓Plain-language summaries of every change
What support looks like in healthcare, manufacturing and sales
Healthcare software maintenance and support carries extra weight. Our healthcare systems are fully HIPAA compliant, we sign BAAs and any other compliance agreements you need, and a HIPAA-trained team member stays involved after launch. Audit logs are reviewed, access is kept to what each role needs, and any change touching patient data is documented. For FDA-regulated work, we maintain the audit trails built for 21 CFR Part 11 so your records stay defensible.
Manufacturers need their operations platform working when the shift starts. With a system like our Industrial Operations Platform, support means keeping quotes, inventory, quality and field service connected so leaders can keep managing by exception. Sales teams need the CRM and commission logic to stay right, because one wrong payout costs trust. In Rep Hub, that means watching the signed and paid trigger that starts delivery and commissions.
The same care applies to every other industry, from tenant, owner and staff portals like Veritas Property Management to whatever system your business runs on.
How requests reach us and what you hear back
You shouldn't need a ticketing manual to ask for help. We agree with you up front on how to reach us, what counts as urgent, and who on your side can approve changes. Requests are logged so nothing depends on anyone's memory, and each one gets a reply that says what we found and what happens next.
You also get summaries in plain language: updates applied, issues fixed, improvements shipped, and anything you should plan for, such as a vendor retiring a feature you depend on. An owner in Round Rock, Mueller or San Marcos should be able to read one quickly and know exactly where their software stands.
- An agreed contact path and urgency levels
- Logged requests with written replies
- Plain-language summaries of all changes
- Advance notice of vendor changes that affect you
The system handles
- Uptime and error alerts
- Backups
- Dependency checks
Your people decide
- Prioritising improvements
- Planning bigger changes
- Reviewing reports
Your code, your data, your choice
Support should never feel like a lock. Clients own the code and data for everything we build, and that does not change while we maintain it. Repositories, hosting accounts and vendor logins stay in your name, with access granted to us rather than the other way around.
Documentation stays current as we work, so if you hire an in-house developer or change partners later, they inherit a system they can understand. Most clients stay because the arrangement works, and that is the only reason we want anyone to stay.
