[ Cleveland and Northeast Ohio ]

Custom software and automation for Cleveland and Northeast Ohio

Wagenberg Technology Group builds and tests software, AI workflows and automation for small and mid-size teams, then hands it over working.

Who this is for

Owners and operations leaders in Northeast Ohio who still run a process in spreadsheets, email threads or repeated re-entry, and want it replaced by something their team can use and own.

What we build

Three kinds of engagement, each scoped in writing:

• Custom software: internal web apps, APIs, databases and multi-user platforms, built in TypeScript and Postgres.
• Workflow automation and AI workflows: scripts and integrations that take the copying and pasting out of your week, with AI only where it saves real time and a person reviewing the output.
• QA and launch readiness: testing by role and by device before launch, with written findings and a retest of every fix.

How a first project works

• Map. We learn how the work runs today and where it breaks. You receive a written scope: what gets built, what does not, and how we will know it works.
• Build. We build in small steps on a staging copy, never on your live system.
• Test. We test by role and by device, the way your people will use it, and retest every fix.
• Hand over. Code, documentation and access in your own accounts, as set out in the signed agreement.

Where we work

• Wagenberg Technology Group LLC is an Ohio limited liability company serving Northeast Ohio.
• Thomas Wagenberg, the founder, does the engineering himself, from the first scoping call to the handover.
• Meetings are held by video.
• We work remotely with teams across the United States.

What we do not do

So the scope is clear from the start:

• Regulated production deployments without the contractual rights and safeguards in place.
• Promises of time or money saved before the current process has been measured.
• IT support, hosting or marketing. We focus on building, automating and testing software.

Proof

See A launch-readiness review: sample findings and retests and Human-reviewed document extraction: a working demonstration with its failures, demonstrations built with invented data. Each service page sets out what that engagement delivers and what it does not include.

Questions about a first project

What does a first project include?

A written scope, a build on a staging copy, testing by role and by device, and a handover with code, documentation and access in your own accounts. The size of a first project and its exact terms are set in the signed agreement.

Who owns the code?

Code written specifically for you becomes yours once it is fully paid for, subject to the signed agreement. Our preexisting tools and code, and third-party materials, are not transferred.

What happens after launch?

The aim is a system your team can run without us. There is no automatic fix period; support after launch is available only under an agreed contract.