Intake and request routing
Forms that capture requests properly and send them to the right person.
Internal tools are the software your own team uses to get work done: intake forms, approval flows, tracking, and reporting. They are well suited to fast delivery because the requirements already exist. Somebody is doing the process by hand right now, and that manual process is the specification.
Timelines are examples, not commitments. Every engagement is governed by its own written statement of work and agreement.
You will recognize at least one of these:
Each of those is a workflow with known requirements, a known group of users, and a before-and-after you can measure. That is exactly why internal tools can be built quickly.
Forms that capture requests properly and send them to the right person.
Multi-step approvals with a record of who decided what, and when.
For anything your business moves through stages, from jobs to contracts.
The monthly report, generated from live data instead of built by hand.
For the data your team currently maintains in spreadsheets.
Tools that put leading AI models to work for your team. We rolled out an AI portal to 500 users in under two weeks.
Forty people on a $45-per-seat tool is $21,600 a year, every year, and it rises. A custom tool built for exactly those forty people at $28,000 costs about $4,000 a year to host and maintain. Counting that, it pays back in about nineteen months, then saves roughly $17,600 a year.
That math is real, and it is incomplete. Per-seat software also gives you a product roadmap, a support organization, and compliance certifications someone else paid for. Do not build to save money on a tool that already fits. Build when it does not fit.
Prices and timelines here are examples to help you plan, not a quote, an offer, or a contract. Every engagement is governed by its own written statement of work and agreement.
The users are your own team, the process is already documented in the form of someone doing it, and there is no marketing site to design and no app store review. Internal tools also rarely need compliance certification.
A single-workflow tool can ship in as little as five business days, which makes an internal tool the least expensive way to find out whether custom software works for your business.
| Tool | Typical timeline | Typical budget |
|---|---|---|
| One workflow, one or two user roles | About 5 business days | Under $10,000 |
| Multi-role tool with integrations and reporting | 2–5 weeks | $18,000–$45,000 |
Prices and timelines here are examples to help you plan, not a quote, an offer, or a contract. Every engagement is governed by its own written statement of work and agreement.
See the full pricing page for every tier.
What the workflow is, who uses it, what it connects to, whether data has to come along, and what compliance applies. We will tell you on that call if you should buy something instead, and if the scope you have in mind does not fit the date you have in mind.
Within a few business days of that call, with a delivery date on it. Fixed price rather than hourly, so the risk of the work taking longer is ours rather than yours. If we deliver late, monetary penalties apply, on terms set out in your statement of work.
You see the software working rather than described, typically twice a week. You should never have to ask where the project stands.
Deployed to your infrastructure, with a walkthrough, written handover, and the source code in a repository you control. Stephen sees every engagement through to this point personally. Nothing is handed off at eighty percent.
All the work is done by the True Cedar team and completed by US-based resources. We do not outsource any of the work. This describes how we typically work; each engagement's terms are set out in its own written statement of work and agreement.
An internal tool covering one workflow typically comes in under $10,000 and ships in about five business days. Multi-role tools with integrations and reporting run $18,000 to $45,000. These are examples; each project's price is set in its statement of work.
Replace it when more than one person maintains it, when its accuracy matters to the business, when people have built workarounds around it, or when it only works if one particular person is available. Keep the spreadsheet when it is genuinely one person's working file.
Often, above about thirty or forty users. Forty seats at $45 a month is $21,600 a year, against a one-time build plus 5 to 20 percent of the build cost each year in maintenance. But per-seat software also buys a roadmap, support, and compliance certifications. Build because the tool does not fit your process, not only to save money.
A single-workflow tool can ship in as little as five business days. Multi-role tools with integrations and reporting take two to five weeks. Each project's timeline is set out in its statement of work.
Stop re-keying data between the systems your tool touches.
Start with the one workflow that matters most.
The full custom web application service.
Show us the file everyone works around. We will tell you what it would take to replace it, and whether it is worth replacing at all.