Software
Internal Tools & Dashboards
The numbers you need are in four systems nobody has joined up.
Small tools and reporting dashboards for the jobs a business does repeatedly: internal admin screens, operational dashboards, and interfaces over data that currently only exists inside other systems.
Built against the systems you already run rather than replacing them, and scoped tightly — an internal tool that tries to become a platform stops being worth its cost.
What this covers
- Internal tools
- Dashboards
What you get
- Scoped tool or dashboard
- Included
- The specific job, built.
- Data connections
- Included
- To the systems that hold the data, using their supported interfaces.
- Access controls
- Included
- Who sees what, agreed with you.
- Documentation
- Included
- What it reads, what it writes and how it is deployed.
How it runs, and what it asks of you
The six stages are the same on every Gridsmith engagement. Where your own time is listed, it is the part of a project that is worth knowing before it starts.
- Consultation
- We look at the current system, who maintains it, where it is hosted and what actually needs to change.
- Planning & Scope
- Scope is written as what the system will do, what it will not do, and who owns each account and environment at the end.
- Approval & Start
- Work starts once scope is agreed. Repository, environment and access arrangements are settled first, on the terms the written agreement sets out.
- Design, Development & Updates
- Built in reviewable increments on an environment you can see, rather than revealed at the end.
- Delivery
- Handover covers the running system, written documentation of how it is deployed, and the source-code and account arrangements the written agreement sets out.
- Support (if applicable)
- Maintenance, monitoring and further development are scoped separately rather than assumed — as further work or as an ongoing engagement.