Inframappa

Inframappa's operations department ran its projects on a manual spreadsheet process. Wrike existed in the company, but only the software development and publishing teams used it. Everywhere else work moved through email, chat, and spreadsheets, so data sat in silos and follow-ups were missed. The work itself has a clear shape. A project contains one or more campuses, and every campus moves through four phases, Discovery, Production, Field Verification, and Publish. The operations lead needed his team managing all of it inside one platform with real tracking and reporting.

We used to implement and support Wrike as a partner, and this is that work. It began with a consultation in late summer 2025, a demonstration to company leadership of dashboards, request forms, blueprints, workload management, and approvals, which ended in a decision to roll Wrike out gradually, starting with the data teams. The implementation followed that fall as a fixed-scope engagement through Upwork.

We built a dedicated Operations space with a nested Portfolio, Project, Campus hierarchy matching the existing sheet, custom fields for Project ID, Campus, Phase, Status, Weight, Completion %, Priority, and Budgeted vs Actual Hours, status workflows reflecting phase progress, and task templates for the four phases. A request form captures the project name, ID, and number of campuses, and a reusable blueprint expands that request into the right number of campuses with the full four-phase task tree, default assignees with fallback logic, and dependencies in sequence. Automations stamp completion dates, flag overdue work, and roll up completion percentages. Three dashboards cover project progress by phase, overdue and upcoming tasks, and user workload. We closed with two recorded training sessions and built the first live projects together with the team.

Creating a project through the request form now produces the campuses and tasks automatically, which is the piece the spreadsheet could never do. The operations team tracks phase progress, hours, and workload in one place instead of a sheet plus memory. Weekly check-in calls ran through the rollout, and recorded training sessions continued into early 2026 as more of the team came on.

Given the same problem now we would build Inframappa a production tracker of their own that holds projects, campuses, the four-phase pipeline, request intake, and workload views in one owned system with unlimited users, instead of a licensed seat for everyone who touches a task. The Wrike build works and the team runs it. A custom build would remove the per-seat bill and let the campus model live in a database designed for exactly that shape.