Managed, cloud and software

Custom Software Development in Central Texas

Engineer Austin's software development team builds internal business applications, integrations, automation and reporting for Central Texas organizations that have outgrown spreadsheets and off-the-shelf tools. You own the code and the data, every release passes a test environment before it reaches production, and each one can be rolled back.

Custom software: an application window listing service requests, integrated with Microsoft 365 and a database, above a release pipeline from dev to test to canary to production with a rollback loop Service requests IDSitePriorityStatus SR-426Water plantHigh In progress SR-427City hallNormal Open SR-428ClinicLow Closed SR-429YardNormal Open role-based access · audit log · exports Microsoft 365 single sign-on · mail Database backed up nightly Release pipeline devtestcanaryproduction rollback
What this includes

Applications, integrations, automation and reporting

  • Internal business applications and portals for service requests, quotes, invoices, inventory, parts and supplier catalogs, recurring work and contracts, built around how your staff actually work.
  • Integrations between line-of-business systems so the same record is not typed into two places and the two never disagree.
  • Automation and scripting. PowerShell for Windows and Active Directory tasks, RouterOS scripting for network devices, scheduled jobs that replace a recurring manual chore.
  • Reporting and data extraction, including from hosted software that offers no export or API, with the method written down and the data quality checked and corrected.
  • Document automation. Proposals, reports, checklists and letters generated from your data into Word and PDF, with revision control built in.
  • Dashboards and analytics that put the numbers a manager asks for every week on one page, such as a twelve-month volume study built from carrier call records with exact counts rather than estimates.
  • Automation with AI components, reviewed by people. Classification, summarization or drafting steps inside a workflow, with a person approving the output before it acts on your records.
  • Certificate and hosting automation so the application you own renews its own certificates and backs up its own database without anyone remembering to.
How we approach it

Discover, scope, build, deliver

Discovery

We sit with the people who will use the application and write down what they do today, where the data lives and what a good outcome looks like. The result is a short scope document you can hand to anyone, including another developer.

Scope and quote

Work is quoted as a fixed fee or in staged releases, each with a defined deliverable. Nothing is built without written approval, and we correct our own mistakes at no charge, under the terms of our written agreement.

Build and test

Every change runs through an automated test suite and a test environment that mirrors production before it reaches your users. Releases are versioned, and the database is backed up before every deployment with automatic rollback if the release fails.

Deliver and maintain

You receive the source code, the deployment procedure and user documentation. Hosting, backups and updates can continue under the Managed Service Program, or you can take it all in-house. Either way, the code and data are yours.

What we build with

We build with modern, widely used web frameworks and proven open-source databases, hosted on hardened Linux with automatic TLS certificates and versioned, scripted deployments. Applications integrate with Microsoft 365 where your people already are, and with the Windows, Active Directory and network platforms we manage every day. We keep the stack ordinary on purpose: an application built on widely used, well-documented components can be maintained by any competent developer, which is part of what makes it yours.

Dependencies are pinned and the upgrade path is written down. The stack is re-evaluated each year, and our release checklist grows whenever a release teaches us something.

How AI speeds this up for you

Routine code, test cases and user documentation are drafted in hours rather than days, so a fixed-fee project spends its budget on the parts that need judgment: your workflow, your data and the edge cases your staff know about. Every change the tooling proposes is read by a developer and logged, the review, test and rollback gates stay exactly where they were, and the tooling never holds write access to your production systems. How we use AI.

What you receive

The code, the data and the documentation

  • A scope document from discovery, in plain language.
  • The complete source code, under your ownership.
  • A test environment separate from production, with the release procedure written down.
  • Versioned releases with a change log and a rollback path for each.
  • Scheduled database backups to independent storage, with the restore tested.
  • User documentation and an administrator handoff.
  • Your data in an open format you can export at any time.
  • A maintenance arrangement, if you want one, on the same monthly invoice as your other services.
Why an engineering firm

Documented, tested and accountable

Software written for a small organization tends to be written once, by one person, and left undocumented. Ours is built on engineering principles under a licensed engineering firm: requirements and acceptance criteria agreed before work starts, a change log, a test gate before production, a rollback for every release, and a design proportionate to the problem rather than a platform you will never fill. Because we also run the servers, networks and Microsoft 365 tenants the software connects to, integration problems are solved by one firm rather than argued between two.

Engineer Austin is Texas Registered Engineering Firm F‑15739; our team does the work to house standards set by our licensed Professional Engineer.

Who this is for

Organizations with a process living in spreadsheets, email and memory: service and field companies tracking work orders, quotes and invoices; districts and cities with records to report to a board; medical and professional offices with data in a hosted system they cannot get out; retailers that need customer and purchase records pulled from a point-of-sale system; and any business that needs two systems to talk to each other and has been told they cannot.

Most of our software clients are also Managed Service Program clients, but that is not a requirement. Hosting runs on the Linux platforms described under servers and virtualization.

We run our own business on our software. EA Command, the system behind our ticketing, scheduling, quoting and invoicing, was built by this team and is now offered to other managed service providers.

FAQ

Custom software, answered plainly

Do we own the code?

Yes. The source code, the database and the documentation are yours. We deliver the code with the deployment procedure so another developer could take it over, and your data stays in an open database format you can export at any time. We build on widely used components on purpose so the application does not depend on us to keep running.

What happens if a release breaks something?

It rolls back. Every release is first deployed to a test environment that mirrors production and must pass an automated test suite there. Before the production deployment the database is backed up, and if the release fails its checks the previous version is restored automatically. Releases are versioned, so we can also return to any earlier one on request.

Do we have to be a managed IT client?

No. Software work is quoted on its own, as a fixed fee under a written agreement. Most of our software clients are also on the Managed Service Program because we already run the systems the software connects to, and hosting and maintenance can be added as a line on that invoice, but a standalone project is welcome.

Can you get our data out of a system that has no export?

Usually. Many hosted applications have no export or API but still deliver data to a web browser, and that path can be read in a controlled, paced way that respects the vendor's service. We document the method, check the results for duplicates and errors, correct what we find, and deliver the data with a written description of how it was obtained.

How do you use AI in development?

Our developers use AI assistants for routine work such as drafting code, tests and documentation, inside tooling that requires approval before anything runs. Every proposed change is read by a developer and passes the same test and rollback gates as any other change, and each action is logged. The tooling never holds write access to your production systems; people do, under written rules of engagement.

Where will the application be hosted?

That is decided in discovery. Options are a Linux server in your own environment, a system we operate for you, or a cloud host you already use. In every case the application runs on hardened Linux with automatic certificates, scheduled database backups to independent storage and a tested restore. You hold the credentials, and the hosting can move if your needs change.

Start with a written assessment.

Tell us what you have and what is not working. Someone from our team, not a salesperson, replies within one business day by email or phone, and brings in our engineer when your request needs one. The assessment report is yours to keep whether or not you buy anything.

Call (512) 481-2710 Request an assessment