The cost to add a staff directory depends on whether it is a small set of manually managed profiles or a searchable system connected to roles, locations, availability, and contact routing. The content workflow matters as much as the profile page.
Define the directory's purpose
Decide whether customers need to find a person, department, service owner, location, language, credential, or contact route. A focused directory costs less than a staff database with many filters and permissions.
Scope profile content and ownership
List name, role, service, location, biography, photo, credentials, languages, availability, and contact path. Define who approves the content, how departures are handled, and which details should not be public.
Price search, filters, and integration
Account for categories, locations, mobile behavior, accessibility, CMS fields, structured data, forms, calendars, CRM, and directory sync. A static directory and a real-time team finder have very different maintenance needs.
The about-page trust checklist and page count conversion checklist help decide what belongs on the public site.
Include change and privacy controls
Estimate approval, effective dates, review reminders, photo rights, contact privacy, redirects, and profile retirement. Make sure a former employee does not remain the visible owner of a live service.
Ask for a lifecycle estimate
Provide sample profiles, search needs, locations, roles, integrations, and update frequency. Confirm what the quote includes for content entry, training, accessibility testing, and ongoing changes.
Staff profiles becoming stale or hard to route? Ask Vertinus to scope a directory around real customer questions.