Discovery week
Five days with your stakeholders producing an architecture, a backlog and a defensible estimate.
Building software since 2012
Senior engineers, embedded, shipping every two weeks
We take on the projects your team does not have capacity for, custom applications, legacy migrations and the internal tools quietly costing you a full time salary in manual work.
13 yrsin business
9 yrsavg engineer experience
2 wkdelivery cycle
62%of revenue from repeat clients
Engagements
Pick a team or pick a project
Monthly team engagements or fixed scope projects, both quoted after a paid discovery week.
Embedded product team
Two engineers, a designer and a lead working in your tools and standups, monthly rolling.
Fixed scope project
Defined deliverable, fixed price, fixed date, with change requests priced before any work starts.
Legacy platform migration
Moving off an unsupported framework or database incrementally, with the old system running throughout.
Internal tools and automation
Replacing the spreadsheet plus email process that is silently costing you a headcount.
Fractional CTO
A senior technologist in your leadership meetings for hiring, architecture and vendor decisions.
About Rivet
No juniors billed as seniors, no bench to feed
Rivet has been at this since 2012 and deliberately stays around twenty five people. Every engineer we put on your project has at least seven years of experience and is a full time employee, not a subcontractor found last week. We only take on what we can staff properly, which means we turn work away most quarters.
•Working software in your staging environment every two weeks, always
•You own the code and infrastructure from day one, in your accounts
•Weekly written status with actual hours against estimate, no surprises at invoice
Reviews
What clients tell us
“Our previous agency showed us slides for four months. Rivet had a working staging environment in week two and we never went a fortnight without something to click.”
Jennifer O., COO, insurance services
“The migration off our old platform took eleven months and we never had a day of downtime. They ran both systems in parallel the whole way.”
Sam A., VP Engineering, logistics
“They talked us out of a build in the discovery week and pointed us at an off the shelf product instead. That cost them a project and earned them the next three.”
Priyanka R., Director of Operations
FAQ
Working with an outside team
Fixed price or monthly team, which should we choose?
Fixed price works when the scope is genuinely knowable, such as replacing a well understood internal tool. Monthly teams work when you are building a product and will learn things that change the plan. We will tell you which one your project actually is during discovery, and we have talked plenty of clients out of a fixed bid that would have hurt them.
Why is discovery paid?
Because a real estimate needs five days with your stakeholders, your existing systems and your data, and that is work. Free discovery is a sales call, and it produces the estimates that turn into change orders. You keep the architecture document and backlog whether or not you hire us.
Who owns the code and where does it live?
You do, in your repository, under your organization, in your cloud accounts, from the first commit. We do not use proprietary frameworks and we do not hold infrastructure hostage. Handover documentation is written as we go, not assembled in a panic at the end.
Will we work with the same people throughout?
Yes. You meet your actual team before you sign, and they stay on your project. If someone has to change, for a departure or parental leave, we tell you in advance, overlap them for at least two weeks and do not bill for the ramp up time of the replacement.
Contact
Tell us what is stuck
A thirty minute call is usually enough for us to say whether this is a project we should take, and if not, who we would send you to.
Phone(778) 555-0178
Address316 W Washington Ave, Suite 500, Madison, Wisconsin
HoursMon to Fri 8am to 6pm CT
AreaUnited States, remote with quarterly on site