Most small app studios do not lose money on the build. They lose it in the gaps between four spreadsheets: the project list one person maintains, the sprint board in a chat thread, the hours everyone means to log on Friday, and the invoice somebody rebuilds by hand at month end. The App Development Project Management System Web App closes those gaps by putting all of it in one Google Apps Script application, running over a Google Sheets database in your own Drive.
It ships as a sign-in screen plus 17 modules. Running setup once builds 17 sheets and seeds 11,793 rows of demo data – a fictional 30-person studio called Northwind Labs with 26 projects, 22 clients, 268 sprints, 3,108 tasks, 515 defects, 115 releases, 7,240 timesheet lines and 77 invoices – so no screen and no report is empty the first time you open it. Every one of those records is demo data and can be deleted or reseeded in one click. App Development Project Management System Web App
The Sign-In Screen
There is no public area and no self-registration – one username-and-password card guards the whole app. An administrator creates accounts in User Management, and the role attached to each account decides which of the 17 modules show up in the sidebar afterwards.
🚀 Try the Live Demo Before You Buy
We have deployed this web app in our own Google account so you can test every page, every role and every report – with the seeded demo data – before purchasing. No signup, no email required.
🔑 Test Login Credentials
Sign in as admin to see everything, including User Management, List Management, Settings and the Audit Log. Then sign in as dev and watch two-thirds of the sidebar disappear – that is the role model working. All six seeded roles are listed below.
💡 These are public demo logins on a shared, self-resetting demo instance – not a customer deployment and not anyone’s live data. Other visitors are signed in at the same time and the records reset, so treat everything you see there as demo data. After purchase you get the full source (Code.gs + Index.html) and a deployment guide, and you stand up your own private copy in your own Google account.
Key Features of the App Development Project Management System Web App
- Six roles enforced on the server. The Role permissions tab is a grid of module against action – view, create, edit, delete, export, approve – and the app checks it on every request, not only when it draws the sidebar.
- One active sprint per project. The server refuses a second one. Closing a sprint recomputes its completed points from the board and can roll unfinished work into the next sprint.
- Logged hours come from the timesheet. You cannot type hours onto a task, so a task can never claim time nobody booked. Nobody can book more than 8.5 hours against a single day.
- Defects are tied to the release they were found in and to the task that introduced them, with target resolution dates derived from severity when you do not set one yourself.
- Approved billable hours become an invoice with one button. Total is always subtotal plus tax; balance is always total less payments.
- Ten exportable reports across delivery, quality, people and commercial, each with a date range plus project and client filters, each printable at your chosen paper size.
- Excel and CSV export on every table – and it exports the filtered view, not the whole sheet.
- 32 editable dropdown lists holding 193 seeded values drive every select box in the app, so you can match your own vocabulary without opening the code.
- A full audit log of who did what in which module, plus the server error log, filterable by user, module, action and date range. App Development Project Management System Web App
Every Page in the App Development Project Management System Web App
Delivery Dashboard
Twelve KPI cards covering delivery, quality, people and money, with a month picker at the top right. In the demo data that reads 15 active projects of 26, 6 flagged at risk, 302 open tasks with 21 past due, 52 open defects, 64.8% utilisation, 84.8% on-time releases and $248,065 in receivables. Below the cards sit a six-month trend of tasks completed against defects raised, a portfolio-by-status donut, recent sprint velocity and where the last 90 days of hours went. App Development Project Management System Web App
Projects
The portfolio register. Every build carries live progress, budget burn, hours logged, open tasks, open defects and a target date, with status and health badges you can filter on alongside platform and client. Opening a row gives you that project’s milestone schedule, sprint history, releases, contributors and invoices.
Sprints
Sprint planning and velocity across the whole portfolio. A bar chart plots the last ten closed sprints, and the Sprints in flight panel lists each active sprint with points done, tasks done, hours logged and days remaining – the demo shows 15 active sprints and 579 points in flight, 180 of them already done. App Development Project Management System Web App
Tasks and the Sprint Board
A five-column board – To Do, In Progress, In Review, Blocked, Done – over whichever sprint you select, plus an All tasks tab holding the full filterable backlog. Each card shows its ID, assignee, story points and work type, and the buttons on the card move it between columns. App Development Project Management System Web App
Defects
Every defect raised against a build, ordered by severity so the painful ones sit at the top. Two donuts break the open queue down by severity and by environment, a bar chart shows which projects carry the most, and the register itself records the version each defect was found in along with its age against target.
Releases
Version and build history per project: channel, target date, shipped date, store status and slip against target. A donut splits releases by channel and a bar chart ranks versions shipped per project. Marking a release shipped stamps the date and the approver.
Timesheets
Three views over the same hours – a filterable entry list, a weekly grid per person, and an approval queue with bulk approve and reject. Charts split the period by activity type, by person and by project. The demo period holds 3,746.1 hours across 1,229 entries, 80.8% of them billable, with 209 awaiting approval.
Invoices
Milestone and time-and-materials billing built from approved hours, with payments received and the receivables still outstanding. A receivables ageing chart buckets the balance and an invoiced-by-client bar ranks the accounts. The Bill approved hours button is what turns the timesheet into a document.
Reports
Ten reports in four groups. Delivery: Project Portfolio, Sprint Velocity, Task Throughput. Quality: Bug / Defect, Release History. People: Timesheet & Utilisation, Team Workload. Commercial: Client Revenue, Invoice Ageing, Project Profitability. Each takes a date range plus project and client filters, exports to Excel or CSV, and prints.
Team, Clients and the Administration Modules
Five more pages complete the app and are not pictured above. Team is the roster with live workload – open tasks, points in flight, hours in the last thirty days against contracted capacity – plus the cost and billable rates that drive the profitability report. Clients is the account directory with project counts, invoiced value and outstanding balance. User Management holds the accounts list and the role-permissions grid. List Management is where all 32 dropdown lists live, reorderable and deactivatable. Settings has ten tabs – Business, Finance, Numbering, Operations, Print, Email, Theme, Security, Archive and Maintenance – covering the studio name and address, ID prefixes, tax and currency defaults, print size, colours, password policy and the database archive. There is also a Help page documenting every module and a Get More Templates page.
App Development Project Management System Web App vs. a Shared Spreadsheet vs. Paid Delivery SaaS – Feature Comparison
| This Web App | A shared spreadsheet | Paid delivery SaaS | |
|---|---|---|---|
| Cost | One-time purchase | Free with your existing account | Recurring per-seat subscription |
| Platform | Google Apps Script + Google Sheets | Google Sheets or Excel | Vendor-hosted |
| Setup time | About 15 minutes: paste two files, deploy, run setup | Minutes to start, weeks to make it reliable | Account setup plus configuration |
| Real-time team collaboration | Yes, multiple signed-in users | Yes, but everyone sees everything | Yes |
| Mobile access | Responsive in any browser | Sheets or Excel mobile app | Native apps |
| Role-based permissions | Six roles on a module-by-action grid | File-level sharing only | Yes |
| Timesheet feeds the invoice | Yes, approved hours bill in one click | Manual re-keying | Often a paid add-on or second product |
| Customisable fields | 32 editable lists, and the source is yours | Fully, by hand | Within what the vendor exposes |
| Share with a link | Yes, your deployment URL plus an account | Yes, but sharing is all-or-nothing | Yes, by invited seat |
| Who holds the data | Your own Google Drive | Your own Drive or OneDrive | The vendor |
| Year-1 cost at 5 users | The purchase price, once | Nothing, plus your maintenance hours | Five seats, renewed annually |
Who Should Use This Template
It suits app development studios and small software agencies of roughly 5 to 40 people who bill clients for build work, freelance developer collectives who need one shared record of projects, hours and invoices, and in-house product teams who want a delivery register their finance colleagues can also read. If you are currently running delivery across a project spreadsheet, a chat thread and a separate invoice file, this replaces all three with one application.
It is a record-keeping system fed by your own data. It does not promise faster delivery, more accurate estimates or conformance to any particular way of working – what it gives you is one place where the projects, the hours and the money are recorded consistently, and reports that read from the same records.
Real-World Use Cases
The Monday portfolio review. A delivery manager opens the dashboard, filters Projects to Health = At Risk or Off Track, then works down the Sprints in flight panel by days remaining. Everything that used to be reconstructed by hand from four files is on two screens.
The release-candidate check. QA cuts a build, opens Releases to confirm what shipped and on which channel, then files defects against that exact version. Because the defect carries the release, the next regression pass knows what to retest.
Month-end billing. A finance officer – who never sees the sprint board, because the role hides it – approves the period’s billable time, clicks Bill approved hours, and works the receivables ageing chart. The invoice ageing and project profitability reports close the month.
Advantages of the App Development Project Management System Web App
- The data model stops the usual spreadsheet errors. Hours cannot be invented on a task, a second sprint cannot be opened on a project, and an invoice balance cannot drift from total minus payments.
- Role separation is real, not cosmetic. Hiding a menu is easy; refusing the request is what matters, and this does the second.
- Nothing is locked. The source is plain, commented JavaScript in two files. Rename the product, add a column, add a sheet, change a rule.
- No recurring cost and no vendor lock-in. The database is an ordinary Google Sheet you can open, export, copy or archive whenever you want.
- It is populated on day one. The seeded demo data means you can evaluate every report before you have entered a single real record – and clear it with one menu item when you are ready.
Opportunities for Improvement
Being honest about the edges is more useful than pretending there are none:
- No integrations. It does not connect to source control, a CI pipeline, or an external issue tracker. Tasks, defects and releases are entered in the app. If your workflow depends on commits creating tickets, this is not that tool.
- Google quotas are the ceiling. Apps Script and Sheets impose execution-time and cell limits. A 30-person studio with 3,000 tasks is comfortable; hundreds of users and hundreds of thousands of rows are not what this is built for.
- It is a responsive web page, not a native mobile app. It works on a phone browser, but a developer logging time on the move will find a laptop easier.
- No accounting integration. Invoices are documents and balances inside this system; it is not a general ledger and it does not talk to your accounting package.
- Security and privacy are your responsibility. The seeded passwords are public, the deployment is yours, and the template makes no data-protection or compliance claim. Change the credentials before anyone real signs in.
Best Practices
- Try the live demo before anything else. Sign in as
admin, then again asdev, and decide whether the role model matches how your studio is organised. - Change every seeded password on your own deployment immediately, delete the accounts you will not use, and set ForcePasswordChange in Settings → Security so new users pick their own.
- Configure Settings before you load data – studio name, ID prefixes, tax defaults, currency, print size and theme. Changing prefixes after you have issued invoices is messier.
- Edit List Management, do not edit code. Your statuses, severities, environments and activity types belong in the 32 lists, where every dropdown reads them.
- Make timesheet approval a weekly habit. Everything downstream – utilisation, profitability, invoices – is built from approved hours, so an approval queue 200 deep quietly breaks the commercial reports.
- Close sprints properly rather than abandoning them. Closing is what recomputes completed points and feeds the velocity chart.
- Use the Archive tab in Settings before the database grows large, and keep a copy of the sheet. It is your data and your backup.
If you are new to deploying Apps Script projects, Google’s own web apps guide covers the Deploy dialog, the execute-as and access settings, and why a code change needs a new version before it goes live.
Explore Relevant Templates
- Consulting Project and Billing Management System Web App – the same projects-hours-invoices loop for a consultancy.
- Recruitment Applicant Tracking System Web App – the hiring pipeline that keeps the roster full.
- Payroll and Salary Management System Web App – pairs with the timesheet side of this system.
- Architect Drawing Approval Management System Web App – review-and-approve workflow in the same style.
- Airport Transfer Management System Web App and Hospital Management System Web App – two more Apps Script systems.
- SaaS Development Dashboard in Power BI – the analytics layer without the data-entry app.
- The full range lives in Web Apps.
Frequently Asked Questions
Can I try it before buying?
Yes. The green box near the top of this post has a live deployed copy of the app and all six seeded logins. Sign in, move a task, raise a defect, run a report, print it. Those credentials are public demo logins on a shared instance that resets – not a customer deployment – so treat everything there as demo data. App Development Project Management System Web App
What do I actually download?
A ZIP containing Code.cs.txt (the full Apps Script backend), Index.txt (the complete front end) and a PDF user manual covering every module, the roles and the deployment steps. Nothing is minified, obfuscated or licence-locked.
Do I need a paid Google Workspace account?
No. It runs on a free personal Google account. Workspace gives you higher Apps Script quotas, which matters more as the team and the data grow. App Development Project Management System Web App
Does it integrate with GitHub, Jira or a CI pipeline?
No. There is no integration with source control, CI or an external tracker. Tasks, defects and releases are entered in the app itself. You have the source if you want to build a bridge yourself. App Development Project Management System Web App
Can I change the roles, fields and colours?
Yes. Roles and their module-by-action permissions are edited in User Management, dropdown values in List Management across 32 lists, and the studio name, ID prefixes, tax defaults, print size and colours in Settings. No code needed for any of that.
Where is the data stored?
In a Google Sheet in your own Google Drive, created by your own deployment. We never see it. You decide who gets an account and how the file is shared, and you remain responsible for any privacy obligations that applies to.
Is the seeded data real?
No. Northwind Labs, its clients, projects and 11,793 rows are generated demo data included so every screen and report is populated on first sign-in. Delete it or reseed it whenever you like.
About the Author
Built by PK – Microsoft Certified Professional with 15+ years of Excel, Google Sheets, and Power BI experience. Founder of NextGenTemplates, reaching 300K+ subscribers across YouTube channels. Every template is hand-built and tested before release.
Conclusion
The App Development Project Management System Web App is not trying to replace your engineering toolchain. It replaces the administrative layer around it – the project list, the sprint record, the hours, the defect register, the release log and the invoices – with one Apps Script application that six different roles can safely share, running on a Google Sheet you own outright.
The most useful thing you can do next costs nothing: open the live demo above, sign in as admin, then sign in again as dev or finance, and see whether the way it separates work matches your studio. If it does, get the App Development Project Management System Web App on NextGenTemplates.com and deploy your own copy in about fifteen minutes.
For walkthroughs of this and other Google Apps Script systems, subscribe to YouTube.com/@NeotechNavigators.
