01 Build
Internal tools and portals
Operating systems for the work nobody sees.
What it is
Internal tools are the software that runs a business behind the curtain. Client portals, admin consoles, reconciliation workflows, inventory and intake systems. We design the operating surface, build the database and access layer, and ship a system that the team actually uses. The output is a tool that replaces the spreadsheet, the Slack thread, and the email chain.
Who it's for
Firms where critical work is held together by spreadsheets and good intentions. Operators who've quoted off-the-shelf tools and found nothing that fits the actual workflow. Teams where the operating cost of the current process is high enough to justify custom.
What's included
- Workflow mapping and operating surface design
- Database schema and access control
- Full portal build with role-based views
- Integrations with existing systems where needed
- Onboarding flow and admin training
- Maintenance and feature work in the Maintain stage
Recent proof
FAQ
- Why not use Notion, Airtable, or Retool?
- Sometimes that's the right answer and we'll say so. The case for custom is usually when the workflow is core to the business, the off-the-shelf compromise costs real time, or the data model doesn't fit a no-code shape.
- How long does an internal portal take to build?
- Four to ten weeks depending on the surface. Simple intake portals on the shorter end, multi-role operating systems on the longer.
- Can multiple teams use the same portal with different views?
- Yes. Role-based access is standard in every build. We design the views around what each role needs to see and do, not around a generic admin template.
- What if the workflow changes after launch?
- That's what the Maintain stage is for. Workflows always change. The build is designed to be modified, not frozen.