Drupal Project Cost Estimation
Help estimate costs and timelines for Drupal projects using a structured approach that breaks down all components.
Source: https://raw.githubusercontent.com/theodorosploumis/notes/refs/heads/master/drupal/cost.md
Extended Parameters: See HELPER.md for automated project analysis, git metrics, advanced task types, and feature-based parameters.
Overview
Provide comprehensive cost estimates by analyzing project scope across multiple dimensions:
- Content structure and architecture
- User management complexity
- Theming and display requirements
- Module requirements (contrib and custom)
- Integration needs
- Timeline and resource allocation
Detailed Cost Breakdown Table
For each project, create estimates using these categories:
| Work/Tasks |
Units |
Title/Description |
Cost/Unit |
Total Cost |
| Operations |
|
|
|
|
| User roles |
count |
Admin, Editor, Authenticated, etc. |
|
|
| User permissions |
count |
Granular permission sets |
|
|
| Content Structure |
|
|
|
|
| Node types (Content types) |
count |
Articles, Pages, Products, etc. |
|
|
| Node fields |
count |
Per-field type complexity |
|
|
| User profiles |
count |
Profile types needed |
|
|
| User profile fields |
count |
Fields per profile |
|
|
| Taxonomy types (Vocabularies) |
count |
Categories, Tags, etc. |
|
|
| Taxonomy fields |
count |
Fields per vocabulary |
|
|
| Forms |
|
|
|
|
| Form types (Webforms) |
count |
Contact forms, applications, etc. |
|
|
| Form fields |
count |
Fields per form |
|
|
| Theming & Display |
|
|
|
|
| Custom template files |
count |
Twig templates, overrides |
|
|
| Ready contrib modules |
count |
Off-the-shelf modules |
|
|
| Custom modules |
count |
Bespoke development |
|
|
| Custom theme(s) |
count |
Themes to build/adapt |
|
|
| Custom mixed content pages |
count |
Panel pages, landing pages |
|
|
| Custom views |
count |
Listings, filters, displays |
|
|
| Custom blocks |
count |
Block plugins, content blocks |
|
|
| Quality & Compliance |
|
|
|
|
| WAI/Accessibility compliance |
hours |
WCAG 2.1 AA implementation |
|
|
| Scale Estimates |
|
|
|
|
| Estimated deadline |
weeks |
Project timeline |
|
|
| Estimated users |
count |
Registered users expected |
|
|
| Estimated contents |
count |
Nodes, terms, media items |
|
|
| Estimated pageviews/traffic |
per month |
Traffic expectations |
|
|
| Integrations |
|
|
|
|
| External services |
count |
APIs, payment gateways, CRM |
|
|
| Website translation(s) |
languages |
Multilingual requirements |
|
|
| Content integrating |
hours |
Migration, import work |
|
|
| Content edit |
hours |
Editorial workflow setup |
|
|
| Other requirements |
|
Custom/specific needs |
|
|
| Contingency |
|
|
|
|
| Unforeseen expenses |
20% |
Buffer for scope changes |
|
|
| TOTAL |
|
|
|
|
Task Group Timeline Summary
Group tasks by phase for timeline visualization:
| Task Groups |
Tasks |
Timeline |
Cost |
| Structure |
Sitemap, Content scheme, Menus, Content types (nodes, taxonomies) |
|
|
| Display |
Theme, Content pages, Views, Blocks, User pages |
|
|
| Users |
Roles, Permissions, Actions, Workflows |
|
|
| Translations |
Content type translations, interface translation |
|
|
| Modules |
Contrib modules selection, Custom modules development |
|
|
| 3rd Party Services |
API integrations, External service connections |
|
|
| TOTAL |
|
|
|
Estimation Guidelines
Complexity Multipliers
- Simple: Basic configuration, minimal custom code (1x)
- Moderate: Some custom theming, standard contrib modules (1.5x)
- Complex: Heavy customization, bespoke modules, multiple integrations (2-3x)
Cost Per Unit Guidelines
- Small site (blog, brochure): $500-$2,000
- Medium site (corporate, small e-commerce): $3,000-$10,000
- Large site (enterprise, complex integrations): $10,000-$50,000+
Timeline Guidelines
- Discovery & Planning: 1-2 weeks
- Development: 2-8 weeks (depending on scope)
- Testing & QA: 1-2 weeks
- Deployment: 3-5 days
Usage
When a user asks for a cost estimate:
- Gather requirements - Ask about project scope, features needed, integrations
- Fill the breakdown table - Estimate units and costs for each row
- Create timeline summary - Group into phases with durations
- Add 20% contingency - Account for unforeseen work
- Present total - Show both detailed breakdown and summary totals
Always remind users that these are estimates and actual costs may vary based on:
- Discovery findings
- Third-party service availability
- Content migration complexity
- Testing and revision rounds
- Ongoing maintenance needs
1---2name: drupaltools-cost-estimation3description: Estimate costs and timeline for Drupal projects using a structured breakdown of tasks, roles, content types, and development work. Use this skill when the user asks for a project quote, cost breakdown, timeline estimation, budget planning, or resource allocation for a Drupal website. Trigger for requests like "how much would this Drupal project cost", "estimate this project", "create a quote", "plan the budget", or any discussion about pricing/timeline for Drupal development.4---56# Drupal Project Cost Estimation78Help estimate costs and timelines for Drupal projects using a structured approach that breaks down all components.910Source: https://raw.githubusercontent.com/theodorosploumis/notes/refs/heads/master/drupal/cost.md1112> **Extended Parameters**: See HELPER.md for automated project analysis, git metrics, advanced task types, and feature-based parameters.1314## Overview1516Provide comprehensive cost estimates by analyzing project scope across multiple dimensions:17- Content structure and architecture18- User management complexity19- Theming and display requirements20- Module requirements (contrib and custom)21- Integration needs22- Timeline and resource allocation2324## Detailed Cost Breakdown Table2526For each project, create estimates using these categories:2728| **Work/Tasks** | **Units** | **Title/Description** | **Cost/Unit** | **Total Cost** |29|----------------|-----------|-----------------------|---------------|----------------|30| **Operations** | | | | |31| User roles | count | Admin, Editor, Authenticated, etc. | | |32| User permissions | count | Granular permission sets | | |33| **Content Structure** | | | | |34| Node types (Content types) | count | Articles, Pages, Products, etc. | | |35| Node fields | count | Per-field type complexity | | |36| User profiles | count | Profile types needed | | |37| User profile fields | count | Fields per profile | | |38| Taxonomy types (Vocabularies) | count | Categories, Tags, etc. | | |39| Taxonomy fields | count | Fields per vocabulary | | |40| **Forms** | | | | |41| Form types (Webforms) | count | Contact forms, applications, etc. | | |42| Form fields | count | Fields per form | | |43| **Theming & Display** | | | | |44| Custom template files | count | Twig templates, overrides | | |45| Ready contrib modules | count | Off-the-shelf modules | | |46| Custom modules | count | Bespoke development | | |47| Custom theme(s) | count | Themes to build/adapt | | |48| Custom mixed content pages | count | Panel pages, landing pages | | |49| Custom views | count | Listings, filters, displays | | |50| Custom blocks | count | Block plugins, content blocks | | |51| **Quality & Compliance** | | | | |52| WAI/Accessibility compliance | hours | WCAG 2.1 AA implementation | | |53| **Scale Estimates** | | | | |54| Estimated deadline | weeks | Project timeline | | |55| Estimated users | count | Registered users expected | | |56| Estimated contents | count | Nodes, terms, media items | | |57| Estimated pageviews/traffic | per month | Traffic expectations | | |58| **Integrations** | | | | |59| External services | count | APIs, payment gateways, CRM | | |60| Website translation(s) | languages | Multilingual requirements | | |61| Content integrating | hours | Migration, import work | | |62| Content edit | hours | Editorial workflow setup | | |63| Other requirements | | Custom/specific needs | | |64| **Contingency** | | | | |65| Unforeseen expenses | 20% | Buffer for scope changes | | |66| **TOTAL** | | | | |6768## Task Group Timeline Summary6970Group tasks by phase for timeline visualization:7172| **Task Groups** | **Tasks** | **Timeline** | **Cost** |73|-----------------|-----------|--------------|----------|74| **Structure** | Sitemap, Content scheme, Menus, Content types (nodes, taxonomies) | | |75| **Display** | Theme, Content pages, Views, Blocks, User pages | | |76| **Users** | Roles, Permissions, Actions, Workflows | | |77| **Translations** | Content type translations, interface translation | | |78| **Modules** | Contrib modules selection, Custom modules development | | |79| **3rd Party Services** | API integrations, External service connections | | |80| **TOTAL** | | | |8182## Estimation Guidelines8384### Complexity Multipliers85- **Simple**: Basic configuration, minimal custom code (1x)86- **Moderate**: Some custom theming, standard contrib modules (1.5x)87- **Complex**: Heavy customization, bespoke modules, multiple integrations (2-3x)8889### Cost Per Unit Guidelines90- **Small site** (blog, brochure): $500-$2,00091- **Medium site** (corporate, small e-commerce): $3,000-$10,00092- **Large site** (enterprise, complex integrations): $10,000-$50,000+9394### Timeline Guidelines95- **Discovery & Planning**: 1-2 weeks96- **Development**: 2-8 weeks (depending on scope)97- **Testing & QA**: 1-2 weeks98- **Deployment**: 3-5 days99100## Usage101102When a user asks for a cost estimate:1031041. **Gather requirements** - Ask about project scope, features needed, integrations1052. **Fill the breakdown table** - Estimate units and costs for each row1063. **Create timeline summary** - Group into phases with durations1074. **Add 20% contingency** - Account for unforeseen work1085. **Present total** - Show both detailed breakdown and summary totals109110Always remind users that these are estimates and actual costs may vary based on:111- Discovery findings112- Third-party service availability113- Content migration complexity114- Testing and revision rounds115- Ongoing maintenance needs