VOGSY implementation guide: Mastering the core configuration

The successful implementation of VOGSY Professional Services Automation (PSA) hinges entirely on the foundational configuration established during the earliest stages of onboarding. This guide details the setup of VOGSY's four essential elements: Companies, practices, and departments (defining your organizational and financial hierarchy), the Project work breakdown structure (WBS) (structuring project architecture and progress tracking), Activities (categorizing billable and non-billable work for accurate cost tracking), and Revenue types (aligning various income streams with your financial system). Getting these four pillars right from day one is critical because every subsequent configuration choice, downstream workflow, and automated reporting capability in VOGSY strictly depends on them. A poorly structured foundation will cascade into misaligned resource management and broken financial integrations, whereas a correctly configured system ensures clear project visibility, maximized resource utilization, and real-time, accurate reporting for C-level management.

The concept: In VOGSY, "Companies" generally represent your distinct legal entities or operating companies. "Departments" are the internal subdivisions within those companies. Departments dictate how resources are grouped, how billability targets are tracked, and how project margins are reported at an aggregate level. "Practices" serve as the overarching grouping layer for your companies and departments, designed specifically to support vertical organizational reporting.

Configuration best practices:

• Align with your P&L: Structure your companies and departments exactly how your executive team and finance department prefer to view profit and loss (P&L) reports.

• Resource grouping: Group employees into departments based on their functional roles or geographic locations so resource managers can easily filter and allocate capacity.

• Leverage practices for vertical reporting: Group active departments or companies under specific practices to streamline C-suite reporting. To support matrix organizations, remember that a department can be assigned to a different practice than its parent company.

• Align companies with finance administration: The configuration of companies should be perfectly aligned with the different administrations you keep in your finance software. When you integrate VOGSY with one or more administrations in multiple software solutions (possibly in different currencies), each administration must exist in VOGSY as a distinct company.

• Clear naming conventions: If your practices span multiple legal entities or companies, establish distinct, recognizable naming conventions (e.g., "Practice A - Company X") so users can easily distinguish them in system dropdowns.

• Avoid over-segmentation: Do not create a separate department for every small team. Excessive departments make high-level reporting cumbersome and dilute resource utilization metrics.

Steering questions for implementation:

• How many distinct legal entities or operating companies need to be tracked financially?

• When the leadership team reviews monthly performance, how do they expect to see the business divided (e.g., by region, practice area, or service line)?

• Do we have overarching practices that span across multiple legal entities or departments requiring consolidated, one-click reporting?

• Who manages employee capacity, and how do they currently filter their talent pool?

The concept: The WBS is the hierarchical skeleton of your projects. In VOGSY, this is broken down into deliverables (overarching milestones or outputs), activities (specific types of work required to produce the deliverable), and tasks. Tasks are the deepest, and optional, level of the WBS and are utilized to manage granular work packages, enabling the tracking of due dates and progress. 

The WBS drives project quoting, budget burn tracking, and progression measurement.

Configuration best practices:

• Standardize for predictability: Create standard WBS templates for your most common project types. This ensures client quotes are consistent and historical margin data can be compared accurately.

• Balance granularity (tasks are optional): A WBS should be detailed enough to track budget risks but broad enough to prevent administrative fatigue. Granular to-do items (tasks) are strictly optional within the project task breakdown structure. It is a choice if you want the breakdown to have this deep granular level. Most customers break projects up only until the activity level.

• Client-centric detail and billing: The level of detail in your progress and billing breakdowns must be defined to reflect exactly what the client expects to see on their invoices. If clients are billed upon the completion of specific phases, ensure those phases are defined as top-level deliverables.

Steering questions for implementation:

• What are the standard phases of our most common service offerings?

• At what level of detail do clients expect to see progress and billing breakdowns on their invoices?

• Do project managers currently struggle with administrative overhead, or do they lack visibility into project budget consumption?

The concept: Activities represent the actual categories of work your team performs (e.g., "Strategic consulting," "UX design," "Project management," "Internal meeting"). Activities form the connective tissue between project budgets, time tracking, and cost control.

Configuration best practices:

• Keep it manageable: Keep your activity list concise, focusing only on categories that have different cost or billing implications. A massive list of activities leads to timesheet errors and user frustration.

• Differentiate billable vs. non-billable: Clearly designate which activities contribute to a resource’s billability targets and project revenue, and which represent internal overhead.

• Map to roles and rates (rate cards): Ensure your activities logically align with your master rate cards so VOGSY can accurately calculate projected costs and revenue when a specific role logs time against an activity.

Steering questions for implementation:

• What are the 5 to 10 core categories of work employees perform daily?

• Which specific actions are billable to clients, and which are considered internal overhead?

• How granular does the finance team need cost-tracking to be to understand project profitability?

The concept: Revenue types categorize the different income streams a business generates. Setting these up correctly is critical because VOGSY maps these revenue types directly to the general ledger (GL) accounts in your integrated accounting software.

Configuration best practices:

• Focus on income streams, not invoicing methods: Revenue types should not be confused with billing or invoicing methods. Normally, revenue types are based on the different income streams a company has. Only when the revenue recognition or revenue forecasting is distinctly different per invoicing method is it advisable to create revenue types for those different invoicing methods.

• Mirror the chart of accounts: Revenue types in VOGSY must perfectly align with the revenue ledger accounts set up by your finance team in your accounting platform (e.g., Xero, QuickBooks, Sage Intacct).

• Support accurate forecasting: Distinct revenue types allow VOGSY to populate revenue forecast charts accurately, letting leadership see exactly how much income is guaranteed (e.g., retainers or subscriptions) versus variable (e.g., Time & Materials).

• Automate compliance: Correctly mapping these types ensures that when a VOGSY invoice is approved, the journal entries sync seamlessly to your accounting system without requiring manual reclassification.

Steering questions for implementation:

• What are the primary income streams for our business?

• How does the finance department categorize revenue on the official chart of accounts?

• Do we have instances where revenue recognition or revenue forecasting is distinctly different based on the invoicing method?