Switchyard Software builds systems that run themselves.
Integrations that end the re-keying, internal tools that retire the spreadsheet, and modernization that keeps the business running while it happens. The engineer who scopes your project is the one who builds it and the one who answers the phone afterward, with five years of owning production systems end to end behind the work.
Three problems that turn into projects
Most of the work Switchyard takes on starts as one of these.
Someone re-keys it.
An order comes in through one system and gets typed into another. Invoices travel from the job software to the accounting software by hand. It holds together until the person who does it is out for a week, and it is quietly wrong a little more often than anyone admits.
Switchyard builds: the integration between the two, with writes that are safe to run twice and a record of everything that moved.
The spreadsheet runs the company.
It started as a tracker. A few years on it has twelve tabs, three people editing it at once, and a formula nobody is willing to touch, and everyone in the office knows it will break long before anyone knows when.
Switchyard builds: the internal tool that replaces it, with the rules written down in code and the history kept.
Nobody can touch the old system.
It still works, which is exactly the problem. The vendor is gone or the original developer is, every change carries risk, and replacing the whole thing at once is a bet the business can't afford to lose.
Switchyard builds: a modernization done in pieces, so the workflows people know stay in place while the parts underneath get replaced one at a time.
Four steps, and you can stop after any of them
Each step ends with something you keep, whether or not the next one happens.
A call
Thirty minutes to describe the problem and hear, honestly, whether software is the right answer and what would be worth looking at first.
FreeA diagnostic
Two weeks inside your process and the tools you already run. It ends with a written plan and a fixed quote, and the fee is credited against the build if you go ahead.
$1,750 · ten hours at the published rateThe build
Priced from the plan, demoed weekly, and every piece lands behind tests before it reaches you.
Fixed priceIt runs
You own the code, the repository, the domain, and the deploy keys. Ongoing care is a retainer or a phone call, whichever suits the business.
Retainers from $349/moWhat these projects usually look like
The typical shape, timeline, and price range for each of the three problems. The diagnostic turns the range into a fixed number.
An integration between two systems that don't talk
Usually two to five weeks after the diagnostic, in the $3,500 to $12,000 range. It ships with a record of every write, so nobody has to wonder what moved, and it keeps working when one side goes down for an afternoon.
An internal tool that replaces the spreadsheet
Usually six to twelve weeks, from $18,000, depending on how many rules the spreadsheet was quietly enforcing. The rules get written down, the history is kept, and the people who lived in the spreadsheet get something that works the way they already think.
A modernization done in pieces
Scoped in phases from $18,000, each phase shipping on its own so the business never waits on the whole. The old system keeps running until the last piece is out, and the workflows people know stay where they are.
Where the experience comes from
Five years of owning production systems end to end, across the kinds of software where being wrong has a cost.
Automation at scale
The scheduling core of a large automation platform, the service that fires every scheduled run, along with its audit logging and the safeguards that keep a bulk action from doing more than it was asked.
Payments and identity
A customer-facing payments SaaS with a single engineer on it: authentication migrated off a deprecated provider without breaking a customer, multi-factor login, and PCI-compliant card processing.
Clinical software
Software used in hospitals, where a legacy interface was moved to the web without disrupting the people relying on it, and a team's performance process was owned week to week.
Software should be boring to operate
Every system Switchyard ships is built to be trusted while nobody is watching it. New behavior ships switched off and is verified against real data before it is turned on. Every change lands behind an automated test suite before it is deployed. Anything that spends money or sends email has a kill switch, and anything that fails lands somewhere a person can read it and replay it. None of that shows up in a demo, and all of it is why the systems keep running a year later.
Recent posts
On automation, integration, and software that keeps working.
- Page speed isn't a vanity metric: how a slow site costs a small restaurant thousands a month Walking through the math on how mobile page-load time translates to lost reservations and online orders for a typical small-business restaurant — and the three fixes that move the needle most.
- The real three-year cost of a 'cheap' website, with the math written out What a $500 small-business website actually costs over three years once you add hosting, redesigns, lost leads, and the cost of fixing what should have been done right the first time.
- Five website mistakes common on small-business sites, and how to spot them on yours A breakdown of five recurring failure patterns on small-business websites in Reading, Wyomissing, and the rest of Berks County — what each one costs, and how to find them yourself.