notes and considerations 

-Header image in posts to be set in 2 columns – mockup

- The featured post needs more separation from the following posts – mockup

Ian I put in the stuff that I could find as well as some extra ideas from my side, I didnt add timing to anything but thought I'd share for your input at this point 

I found a bunch more rapid api links on case studies so asked Lau to update those - I also found one task asking us to link to the MST so that led me to youtube, there's quite a lot in the channel that can be linked to the site to gain that extra boost SEO wise and possibly some of those can become blogs too 

A resources section feels like something that might be nice to compliment the news / blogs so maybe instead of calling it GEMS news (which they want to change to blogs) it should be GEMS resources and we link all resources including videos - not sure 

I also thought that it might be nice to add a "how to get involved " section somewhere which is about contributing towards the whole initiative funding wise 

Not sure if we can mention the Gates Foundation but big hitters like that might find the site so making it easy to contribute feels like a good idea

Other than that, I thought getting Lara to do an audit is a good idea - its 2 years later from when we launched the site so would be good to know what is working and what areas of opportunity exist - 

Edit / add as you see fit 

Ian  have you had a chance to look at this yet? 

Not yet Robyn  

I believe we have everything Phil mentioned on the list - we should work in the knowledge base and see how they want to go about this with a Salesforce implementation - I also think we need to revisit the purpose of the knowledge base so we can make sure whatever we do is geared to the intended audience 

https://resources.docs.salesforce.com/latest/latest/en-us/sfdc/pdf/lightning_knowledge_guide.pdf

https://resources.docs.salesforce.com/latest/latest/en-us/sfdc/pdf/salesforce_knowledge_implementation_guide.pdf

Robyn costing is ready for you. Would you put this into a doc for us, please? I think at this stage we can keep project deliverables vague, as things are bound to change. 

The costing is deliberately high. If they get all their funding through, we can spend this money in the next 6 months; otherwise we'll extend the contract to make the money last as long as is needed. I think it's important to mention that again, in case they've forgot that part of the plan. 

on it, thanks Ian  ! Will share back with you for final approval (aiming to get it done this morning) 

Ian the new proposal - I know they didnt like this format before but lets send it this way and then put it on the old format if needed 

I am not sure if I went too deep on the deliverables so please edit as you see fit 

I added your note about funding to the timelines and notes slide so please check if that's what you had in mind or if that should rather come of the doc and be said on email. Dankie baie! 

https://docs.google.com/presentation/d/1W9ryC4NX8cRKVjKH0f0XTi4k5Oh-pFe517glNOBTwTU/edit#slide=id.g29989f95ef6_0_842

Thanks, Robs. I think this format is ok, but let's add the standard contract (the one I shared with Brightblack as well); then we can remove signatures and Ts and Cs from this doc. 

Would you pass the deliverables through Gemini / ChatGPT for a cleanup? Happy with the content you've put in there :) 

no probs! Thanks Ian  

ps please share the standard contract with me - not sure I remember what that one looks like. thanks Ian  

updated - please do a final check Ian https://docs.google.com/presentation/d/1W9ryC4NX8cRKVjKH0f0XTi4k5Oh-pFe517glNOBTwTU/edit#slide=id.g29989f95ef6_0_847

Here's the Contracts folder: https://drive.google.com/drive/folders/1jjusw-5Sh_YB1rzJ1nt3kyTPPDxKNPtS

Hi Robyn,

Phil and I reviewed the proposal and several comments/edits, bottom line we are thinking of a 9-month contract that could get extended to June 2025 if things are moving slower in the 23K range. See specific comments by page of the proposal:

Page 3:

Under design, remove solutions brochure

Add in reworking existing brochures

Move GEMS leaning into the Design bucket, total of 44 hours

Page 4:

Focus of web is to restructure webpages to be more product and user focused, rather than the current general descriptive content

Remove time for Funding / Partnership sections and Communities of practice

Can you clarify what "download case studies is", we were not sure, and thinking of removing this item as we have no urgent need to edit case studies 

Can you clarify what additional blog functionality is regarding.

Given our current and near future client size, we will not renew Fresh or pursue Salesforce CRM. In these areas, we would be mostly looking for guidance, examples and some testing.

Combine the workflows and knowledge base into one bucket, totaling no more than $6,200

Pages 5, 6, 7 and 8

No comments/edits

Page 9:

Change time frame from 6 to 9 months (July 2024 - March 2025)

Add note that Matogen staff have different bill rates, and that is reflected in the estimate. There is not a fixed hourly rate that GEMS would be billed for all work (I'm worried about accounting doing line by line calc's and getting different numbers when the same number of hours are estimated)

If you could add in the additional info for the clarifying questions via email and then send an updated proposal next week, we will have a final review, and if no other questions I will put request for this contract through UMN finance. 

Best,

Kris