I will build a focused react and typescript internal business tool

I can build focused staff-facing tools such as admin dashboards, intake and review systems, approval workflows, searchable records, reporting utilities, operations tools, and other purpose-built applications for a defined internal process.

A page is one distinct application screen or view with a defined purpose. Tabs, large modal workflows, substantially different states, or separate functional areas may count as additional screens depending on their complexity.

Yes. I can work from an existing design, wireframe, screenshot, style guide, or application. If you do not have one, I can create a practical interface based on the workflow and your existing brand or product style.

Database work can be included when the tool requires it. The exact approach depends on your existing stack, data model, hosting, and requirements. Significant migrations, complex reporting, or large existing datasets may require separate scope.

Yes. Authentication and role-aware behavior can be included when appropriate. Simple existing authentication is usually straightforward. New identity systems, SSO, complex permissions, or enterprise authentication may require additional scope.

Possibly, and that is a common use case. I’ll first look at what the spreadsheet is actually doing. If a focused application would make the process safer, clearer, or easier to manage, we can build around the useful workflow rather than copying every spreadsheet habit.

Yes, when the release process is straightforward and access is appropriate. Hosting, infrastructure, CI/CD changes, permissions, or complex deployment procedures may require separate scope. I’ll confirm that before making production changes.