Built by us
We Build Our Own Tools.Here's What's Actually Running.
This isn't a portfolio of client work — this is the software we run our own operation on, right now. Five systems, what each one replaced, and a straight status on every one, including the one that hasn't met a paying client yet.
Based in North Houston — Serving Businesses Across Texas
Our own stack
Five systems, and what each one replaced.
Every one of these runs the business you're currently reading the website of. Where a system isn't live yet, the card says so in the same size type as everything else.
Client-Onboarding Pipeline
e-sign → PSA → billingProblemSigning a client meant typing the same company, contact, and terms into three systems, then hoping they still agreed a month later. Every retype was a chance to get the billing wrong.
What we builtA signed contract in SignWell creates the company, contact, and agreement in ConnectWise, then the customer and billing setup in QuickBooks — no retyping anywhere in the chain. Three points stop and wait for a human: sending the contract, confirming the deployment, and sending the first invoice.
StatusBuilt and tested end to end on synthetic data. It has not onboarded a client yet — it goes live with our next signed client.
Monthly Billing Engine
agreements in, invoices outProblemRecurring invoices rebuilt by hand every month are a data-entry job, and data-entry jobs drift — the agreement says one thing, the invoice says another, and the client finds out.
What we builtMonthly invoices generate in QuickBooks from ConnectWise agreement data. A drift gate sits in front of the send: when the two disagree, the send is blocked until a person resolves which is right.
StatusBuilt and live-tested.
Review-Request Engine
closed ticket in, drafted ask outProblemThe right moment to ask for a review is right after a ticket closes well — exactly when everyone is starting the next one. Ask by hand and it doesn't happen.
What we builtIt watches closed ConnectWise tickets and drafts the ask off the actual ticket. Draft-first by design: nothing goes out until a person reads it and sends it, because a review ask that lands wrong is worse than none.
StatusBuilt and verified. It goes live when our Google Business Profile review link is armed.
SEO Watchdog
monthly diff against a stored baselineProblemA website quietly loses a title tag, a meta description, a canonical, or a block of structured data, and nobody notices until the rankings move a month later.
What we builtA scheduled job pulls every page on this site and diffs titles, meta descriptions, schema, and canonical tags against a stored baseline. Anything that changed without us changing it raises an alert.
StatusLive, running monthly. The baseline is re-taken every time we deliberately change the site — including for the page you're reading. Everything it watches is public, so it's the most checkable thing here.
Meet Artifacts Pipeline
recordings and transcripts, keptProblemGoogle Meet recordings and transcripts are deleted by the API after 30 days. Anything nobody pulled down inside that window is gone, and you find out when you need it.
What we builtTooling built on the Google Workspace APIs that syncs recordings and transcripts out and archives them before that window closes — a call from two months ago still has a record.
StatusBuilt and running, with a limit we'll name rather than paper over: calendar-linked auto-patching is constrained by the API scopes currently granted to us, so part of that step is still manual. The rescue is reliable; the tool isn't finished.
No percentages, no hours saved, no logo wall
We don't have a clean number for what these systems save us, and inventing one would undercut everything else here. No client logo wall either — these are internal tools, not client deliverables. What we can do is walk you through any of it on a call: the handoffs, the gates, and where it still waits for a person. That's the proof.
Why this is on our website
The client version is the same work, on your systems.
Every system above is connective software between tools that already existed — an e-signature platform, a PSA, an accounting system, a website. That's exactly the work we scope and quote for clients.
Client automations live inside client environments, and publishing anonymized versions you can't verify isn't proof of anything. If any of the five above looks like a problem you have — records typed into three systems, invoices rebuilt by hand, a follow-up nobody remembers, something quietly breaking where nobody's watching — the client version is a scoped project with a fixed fee.
How a project works, and what it costs: automations and integrations · the full automation menu · if the gap is your team rather than your systems, AI training for teams.
Every system on this page is either running or explicitly marked as not yet live — the onboarding pipeline is built and tested but has not onboarded a client yet · No percentages, no hours-saved claims, no placeholder statistics · Client automations aren't shown here; those live inside client systems and aren't ours to publish · Automation work for clients is priced on the automation menu: audits $1,500, fixed-fee builds from $2,500, Automation Care $250–$750/mo · Managed IT is available separately at $125/workstation/mo and $275/server/mo · Same-day response on every ticket · Based in North Houston, serving The Woodlands, Spring, Conroe, Kingwood, and businesses across Texas.
Want the walkthrough?
Fifteen minutes. Pick whichever system on this page you want opened up, and we'll show you what the client version would look like on your stack.
Talk Through Your Workflow →Or call (972) 244-3009 or email support@otherguys.tech — same-day response, in writing.
When your I.T. can’t fix it, the Other Guys can.
Humility | Excellence | Innovation