# [Full “Shape Up” booklet on Basecamp](https://basecamp.com/shapeup)

---

## **Problem**

_Clearly define the core issue or challenge you’re tackling. Explain why it matters, what’s at stake, and who is impacted. This section should set the context and make the reader care about finding a solution._

The focus of this pitch is adding an "Account Add/Edit" Feature to the Admin Side of our internal CRM tool. Currently, Leila uses a python script to generate an account and contact folder for a given account and their contact then uploads that to the webDAV server using the vscode extension. This project will focus on recreating that function in javascript so Alison, Graydon, or any member of our team can easily add an account to the CRM tool. This is will help with organizing customers/accounts to make it easier to track susbscription due dates and renewals. 



## **Appetite**

_Describe the amount of time, resources, and energy you’re willing to invest in solving this problem. This is about setting boundaries and expectations so the scope fits the commitment._

Leila will dedicate two weeks to this project.




## **Solution**

_Lay out your proposed approach to addressing the problem. Focus on the big idea and how it meets the appetite, without going too deep into implementation details._

This project will integrate a Claude.md file into the simtable-crm repository. The programming for this project is pretty simple -- create a set of forms to input account, subscription and customer details into. Next, organize the information from the forms into a payload that
can create the appropriate files + folders to be stored on our webDav server. I anticipate this will take one week with Claude. 

The remaining time in this pitch will go to further organizing and investigating our current customer accounts and determining subscription due dates, prices and lengths.



## **Rabbit Holes**

_Identify potential uncertainties, complexities, or areas that could consume more time than expected. By calling these out early, you can plan to avoid them or decide how to handle them if they arise._

Avoid duplicating accounts...our accounts don't necessarily have good names to make it obvious that account has already been created. What data can we require and check through to make sure an 'account' hasn't already been created with a slightly different name...especially
relevant for the CalFires. 

Avoid duplicating contacts...currently there isn't a page to see our contacts. Possibly implement a listing of our customers by name, so the person inputting data can check if we already have this contact information on our server. If a contact already exists and needs to be linked with a new account, we need to make that an option to 'select existing contact' instead of only displaying a 'new contact' form when asssociating a contact with an account. 



## **No-Gos**

_List the things you will not do, explore, or include in the project. These constraints protect the scope from creeping and keep everyone aligned on the boundaries._

Keeping 'search/filter' functionality out of scope.