Independent engineering practice

Software that keeps working after the invoice is paid.

LTP Microservices is one engineer, start to finish: custom websites, business applications and databases, and the Linux servers they run on.

Start a conversation See the services

One engineer across every layer
  1. Website pages · forms · SEO
  2. Application PHP · business logic · APIs
  3. Database MariaDB · MySQL · reports
  4. Server Linux · cPanel · mail · DNS

What LTP Microservices builds and looks after

Custom Website Development

Websites built as code rather than assembled from a page builder — so they stay fast, stay indexable, and can still be changed in five years.

Business and Database Applications

Internal tools, portals, and reporting systems shaped around how a business actually works, instead of bending the business around packaged software.

Automation and API Integrations

Removing the manual step between two systems: scheduled imports and exports, API integrations, and reports that generate themselves.

Legacy System Modernization

Bringing an old but working system onto supported PHP and database versions without a rewrite and without losing behaviour people depend on.

Maintenance and Support

Ongoing care for sites and applications, so problems are found before a customer finds them.

Security and Hardening

Making a site survive the automated traffic every public site receives, and cleaning up properly when something has already got in.

Technical SEO

The engineering half of search: making a site crawlable, indexable, fast, and unambiguous about what each page is.

Work for Inspec

BEMS and the sites below belong to Inspec (opens in a new tab), independent building enclosure consultants in Chicago, Milwaukee and Minneapolis. LTP Microservices designed and built BEMS, and handles the design and SEO of Inspec’s websites.

Case study

BEMS: Inspec’s Building Envelope Management System

The web system Inspec’s clients use to see the condition of their roofs, walls and paved areas, report leaks and follow every repair. Designed, built and hosted for Inspec by LTP Microservices.

Read the case study BEMS on inspec.com (opens in a new tab)

The BEMS sign-in screen: “B.E.M.S. by Inspec” beside the title “Building Envelope Management System” and the Inspec logo
Screenshot of bems.inspec.com · BEMS © Inspec
The inspec.com home page: “Building enclosure consultants who find the problem before it finds you” over an aerial photograph of commercial buildings
Screenshot of inspec.com · © Inspec

Website design and SEO · Inspec

Inspec (opens in a new tab)

The website for Inspec’s building enclosure consulting practice: roofing, waterproofing, forensic investigations and hygrothermal modeling. Design and SEO by LTP Microservices.

The Roof Consultants Chicago home page: “Commercial Roof Consultants in Chicago” over the Chicago skyline at dusk
Screenshot of roofconsultantschicago.com · © Inspec

Website design and SEO · Inspec, Chicago

Roof Consultants Chicago (opens in a new tab)

The website for Inspec’s Chicago branch: commercial roof inspection, leak investigation and roof replacement consulting across Chicagoland. Design and SEO by LTP Microservices.

More client websites and web applications are on the Work page.

How the work is done

Inspect before changing

Existing systems get read and understood before anything is touched. Code that looks strange is usually solving a problem nobody wrote down, and finding out what that problem was is cheaper than rediscovering it in production.

Own the whole stack

The application, the database, the web server, and the DNS are one system. Being able to work at every layer means a slow page or a bounced email gets diagnosed rather than handed to somebody else.

Prefer less

A dependency is a permanent commitment to somebody else's release schedule. Where a few lines of native code will do, that is what gets written — which is why sites built this way are still maintainable years later.

Leave it documented

Every project ends with a written account of how it is put together, how to deploy it, and what to check when it misbehaves — including the parts that would matter if somebody else took it over.

Have a system that needs building or fixing?

Describe the problem and you will get a direct answer about whether it is worth doing, roughly what it involves, and what it would take.

Start a conversation