CRMs & internal tools
One tool shaped around how your team works, in about a week.
Replace the spreadsheet and the five tools around it with one internal tool: the records, the stages, the permissions and the reports your team actually uses, and nothing it doesn’t.
Prefer to write? Send your requirements
In short
PutThrough builds CRMs and internal tools — sales pipelines, admin panels, inventory and order tracking, and approval workflows — in about a week, at a fixed price agreed in writing after a free scoping call. Each tool is shaped around one core process, with roles and permissions, your existing spreadsheets imported and checked, notifications, reports, an audit trail and tested backups.
01Who it’s for
For teams that have outgrown spreadsheets.
-
Small businesses running on spreadsheets
Clients, orders or inventory spread across sheets and inboxes, with nobody sure which copy is right.
-
Sales teams fighting a generic CRM
You pay for a CRM built for everyone and use a tenth of it. A pipeline built for how you actually sell.
-
Operations teams with a manual process
Approvals, handoffs and status updates done by email and memory. One place where the work moves and everyone can see it.
02Example uses
What a one-week internal tool usually is.
-
Sales pipelines
Deals, stages, contacts and follow-ups, with the reports your team looks at every Monday.
-
Admin panels
A safe way for your team to manage users, content or orders without touching the database.
-
Inventory and order tracking
Stock, orders and fulfillment in one place, with a clear history of who changed what.
-
Approval workflows
Requests, approvers, deadlines and an audit trail, instead of an email chain.
03What fits in a week
One tool, one team, one core process.
Fits in a week
- Your records, fields and stages, as you name them
- Roles and permissions for each part of the team
- Import from your existing spreadsheets
- Email notifications and a weekly summary
- Reports and dashboards for the numbers you track
- Two or three integrations you already use
Needs longer, or a call first
- Several departments’ processes at once
- Large migrations out of a legacy system
- Replacing your accounting software
- Formal compliance programs such as HIPAA or SOC 2
04A sample week
Seven days, one internal tool.
The same seven days as every build, with this product’s work in them. Your week is planned on the scoping call.
- Day 0
Scoping call and fixed quote
How the work moves today, where it breaks, and the one process the tool has to handle first.
- Day 1
Records, stages and roles
The data model, the stages, who can see and change what, and the screens, agreed in writing.
- Days 2–5
Build, in the open
The tool, your data imported from the spreadsheets, notifications and reports. A preview link your team can try every evening.
- Day 6
Harden
Permissions tested per role, the import checked against the originals, backups restored, an audit trail on changes.
- Day 7
Launch and handover
Your team moves over, then a walkthrough for the people who’ll run it and the written handover.
05What you get
What you walk away with.
- The tool, live and in use by your team
- Your existing data imported and checked
- Permissions tested for every role
- An audit trail of who changed what
- Automated backups, with a restore already tested
Plus the standard handover every build ends with: source code, a written handover, a recorded walkthrough and every account in your name. The full Day 7 list
06Stack
Built to be changed as the team changes.
Internal tools change as often as the team does, so they are built on the most common tools we know, in a codebase any web engineer can read.
- Language
- TypeScript
- App
- React and Next.js
- Data and auth
- Postgres, usually through Supabase
- Your email provider, or Resend
07Pricing
A fixed price for a fixed scope.
Your exact price is fixed in writing after the scoping call, before you commit to anything.
After launch, the care plan is from $499 per month.
Prefer to write? Send your requirements
08Questions
01 Why not just use an off-the-shelf CRM?
Often you should, and we’ll say so on the call. A custom tool makes sense when your process is the thing that sets you apart, or when you’re paying for a large product and using a small part of it.
02 Can you import our spreadsheets?
Yes. We import them during the week and check the result against the originals before your team moves over.
03 Can it connect to the tools we already use?
Usually, if they have an API. Two or three integrations fit in the week; we confirm which ones on the scoping call.
04 Who can change it after launch?
Anyone who knows TypeScript and React, which is most web engineers. The handover explains how to add fields, stages and reports.