Software built to work, to be understood, and to be yours.
A software studio in Indiana. We design and build web and mobile software, connect it to the services it depends on, and keep it running after launch.
01 / What we do
Build it, connect it, keep it running.
Three kinds of work and one way of working: scoped in writing, accepted by you, and yours once it is paid.
Build
01The first version of a product, or the rebuild of one that has outgrown how it was made. Web applications, mobile apps, and the systems behind them.
Connect
02The integrations that make a product real: payments, banking and identity providers, booking and ordering platforms, the APIs nobody else wants to touch.
Keep running
03After delivery, a maintenance plan with response times and included requests, or work per request. Either way, what you paid for is yours.
02 / How we work
Nothing starts on a handshake.
Scope, sign-off, payment and release all happen in the client portal, in that order, and each step leaves a record you keep.
There is never a question about where things stand, what was agreed, or what you own.
Open the client portalA written scope
Milestones, each with acceptance criteria a person could check, a price, and a date.
Your sign-off on each milestone
In the portal, on a staging build, before anything is invoiced.
Payment by invoice
Card or bank, and release after payment. Each milestone is yours once it is paid.
A record of all of it
Agreements, acceptances, invoices and releases, kept by the studio and shared with you.
03 / Approach
Pragmatic about tools. Serious about depth.
The work is judged by whether it holds up after launch, so the choices are practical ones and the depth goes where a failure would hurt.
- 01
The practical choice
Proven tools your team can hire for and change later, chosen for the problem in front of us. Something new has to earn its place in your product.
- 02
Depth in the hard parts
Backend and systems work is where the studio is strongest: data, integrations, payments, and the paths that fail quietly. Interfaces are kept clean and functional.
- 03
Honest about the edges
When a problem sits outside what the studio knows well, you hear that first. Then it is learned properly, or it goes to someone who already knows it.
Notes from jeryn.me
If there’s a tool I don’t know, I’ll learn it. If there’s a system I don’t understand, I’ll use all of my time until I do.
My focus is backend and systems-level programming, though designing clean, functional interfaces has come naturally along the way.
If I can’t write it clearly, I don’t understand it yet.
04 / Who does the work
One studio, and the people it trusts.
Jeryn Vicari leads every engagement and is the person you talk to. When a project needs a specialism, or more hands to hold a date, the studio brings in people it has worked with and trusts.
However many people touch the work, you deal with one studio: one agreement, one invoice, one point of contact.
- Your written consent first
- Nobody outside the studio works on your project until you have agreed to it in writing.
- Under the studio's contract
- Anyone brought in works for the studio, not around it. Their work is reviewed by the studio and accepted by you against the same criteria, and the studio answers for it.
- The same terms all the way down
- The same confidentiality applies, and what they build becomes the studio's, so it is yours on payment like everything else.
05 / Also from the studio
Products we build and operate ourselves.
06 / Working with us
Tell us what you want built.
We reply with questions, then a short paid discovery that ends in a written proposal you can take anywhere, then a scope you sign in the portal.
- 01Questions
- 02Paid discovery
- 03Written proposal
- 04Signed scope