<aside> 🤝 This proposal template will be a starting place for you to share why your company should invest in an internal developer portal. Make a copy and fill in the information that makes sense for your team. Find more information on how to shape a proposal here.

</aside>

The problem

Add your unique problems to solve below. We started you out with a couple of options:

Our developers want to spend more time coding

With a distributed architecture and team, our developers feel the pain of software ownership. They spend more time on operational tasks and searching for information than they want.

Efficiency drags:

• Searching for documentation and service owners
  • Documentation is often outdated or sprawling across places. Having API and Tech docs in one location alongside the service information ensures that when something needs attention, the service owner or on-call engineer can find what they need quickly.
• Waiting for platform team to provision a new service or execute an operational task
  • Every operational friction point slows down the release process making the team less efficient.
• <add your unique challenges to this list>

Our [your team name] spends too much time on low-impact work

Our team should be working on ways to automate processes, build dev tools, and help to launch new software faster.

Instead, we’re spending time:

• Searching for services and owners to fix issues or solve problems
• Asking owners to update their docs
• Executing operational tasks for service owners
• <add your unique challenges to this list>

The solution: An internal developer portal

<aside> 🚀 Internal developer portal: Provide developers with access to the tools and knowledge they need to quickly deliver quality software.

</aside>

• Improve visibility across our software ecosystem
• Faster product delivery and time to market