Custom internal tools, client portals and web apps

• Internal tools. The tracker, log or approval queue your team keeps in a shared spreadsheet, rebuilt as one application with your rules written in. In a warehouse that might be the record of accessorial and VAS (value-added services) work that has to reach the invoice, or when the system and the shelf disagree.
• Client portals. A place where your clients check orders, download documents and raise requests without calling your team. Each client sees its own records and nobody else’s, drawn from one record across WMS, TMS and portal.
• CRMs and dashboards. Pipelines, reports and the screen a manager checks each morning, drawn from the systems you already run.
• Websites. Company and service sites with inquiry forms that reach your team. An editable content system is included where the project scopes it.
• Tools for the road. Screens for dispatch, driver check-ins and the paperwork that has to follow a load to the invoice. More for trucking.

We built Microsive Dialer, the calling system our own sales team uses, along with MicroFlow, MicroLead, Microsive CRM and Voice WFM. They are the clearest example of how we work. Software we built and still run.

Why this stack

• Next.js, React and TypeScript: widely used, so any future team can pick up the code.
• PostgreSQL with Prisma: your data sits in a standard database that other tools and teams can read.
• Railway, a managed server, or the setup that suits the app: we deploy and host it, in accounts you own, in a region chosen with you. A US region is an option.

Off-the-shelf software is the right start for many teams. Custom software starts to pay off when your team keeps working around a tool: copying data between systems, tracking approvals in email, or paying for features nobody uses while missing the one you need. If you run a WMS or TMS, we usually build beside it rather than replace it. We replace a system only when that system is a spreadsheet, or something you already want gone. The scope conversation is where we find out whether building is worth it.

1. Scope and quote. A written scope with a fixed quote before the build starts. Changes are quoted before they are done.
2. Regular demos. You work through real screens with sample data while we build.
3. Hand over. The source code and repository are yours. The full detail is on how we work.

We built an applicant tracking system that takes a recruitment agency’s candidate tracking out of spreadsheets, and we run it. Each agency works in its own separate space inside it.

A recruiter moves candidates along a pipeline whose stages the agency defines for itself. What each person can see is decided twice over: by where they sit in the agency’s reporting line, so a manager sees their own team’s records and no one else’s, and by a role the agency writes, which turns individual pages, dashboard panels and actions on or off. The same structure is editable as an org chart you drag people around in.

Around that sit resume screening that ranks a shortlist against a role, invoicing with placement fees, and attendance and leave for the agency’s own staff.