Technivize

Your business runs on a spreadsheet and whatever's in your head.

We come in, watch how the work gets done, and fix one thing in the first week. The week after that we fix the next thing. A few months in, your team has a system they can run without asking you.

Email us [email protected]

How we work

  1. Watch how the work gets done

    The first few days are mostly sitting next to your team while they do their jobs. We're looking for the spots where someone retypes something, waits on someone else, or keeps a private spreadsheet because the official one doesn't work. The problem the owner describes and the problem we find are usually different.

  2. Fix one thing this week

    There's always something we can fix in the first week. Often it's small, like a spreadsheet reorganized so people stop making mistakes in it, or a report that used to take an hour every Tuesday and now takes none. We do that first because it's useful on its own, and because it gets us into your systems before we suggest anything bigger.

  3. Build on it

    The first fix usually shows us the second one. Over a few months the pieces add up to something your team relies on, and the owner stops being the only person who knows how things work.

There's no discovery phase or proposal deck. The first week is spent fixing something.

Job log

A political consulting firm in Florida

They track school board races across the state. When we met them, the whole operation lived in one spreadsheet.

  1. Day one

    One Google Sheet, one tab per district. Someone on staff would open each county's elections website, copy the candidate information into the sheet, and paste in links to the filings. Every tab was formatted a little differently, and it was hard to tell what was current.

    We spent the first day reformatting the sheet so it was easier to read and harder to break. Doing that also taught us how the whole process worked.

  2. That week

    While going through the sheet we noticed that every county's elections site runs on the same software, so the pages all have the same structure. We wrote a scraper that pulls candidate data for every district in Florida and drops it into a new tab in the same sheet. The team kept working the way they always had, with the copying part gone.

  3. A few weeks in

    Once the scraper was running, the sheet had more rows than a spreadsheet handles well. We moved the data into a small web app with logins, so the scraped records and the team's own notes lived in the same place.

  4. Once it was an app

    With a real app we could add things a spreadsheet can't do. The firm can give its own clients a login that only shows their districts. Users can star the candidates they're watching, filter out races they don't care about, and see a changelog of what moved since they last looked.

  5. Now

    We're adding dashboards and alerts, so the team hears about a new filing without having to go look for it.

A spreadsheet turned into a monitoring tool the firm now shares with its own clients. There was never a launch. Each step took a few days, and each one made the next one obvious.

Other work

Websites
Static sites and CMS-backed sites for small businesses, along with the hosting, DNS, and upkeep that come after launch.
An office built for video calls
Cameras, lighting, acoustics, and room layout for a CEO who runs strategy sessions in person and needed remote people in the room. The setup was built around how he already ran the meeting.
Alvo
A group-chat app with lists, tasks, boards, and a calendar inside the conversation. We designed it, built it, and shipped it to iOS and Android. It's in open beta at alvoapp.com.
Inside other companies
Over a decade working across industries on IT, data, automation, and integrations, including the systems work that comes with acquisitions.

What we build

Custom internal software
Web apps, dashboards, scrapers, and connections between the tools you already pay for. Built around how your team works, which is usually the part off-the-shelf software gets wrong.
Web infrastructure and security
Setup, hardening, and upkeep for your public-facing sites. Backups, updates, DNS, and certificates, the things nobody thinks about until they stop working.
Process and workflow fixes
Sometimes the fix is a process change, or cancelling a tool nobody uses. We'll tell you when that's the case instead of building something.

Get in touch

If you can't say exactly what's wrong, that's fine. Most people can't at the start.

[email protected]

Send a few lines about what's annoying at work right now. We'll write back with questions.