<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Projects &amp; Clients on Handbook</title>
    <link>https://handbook.gradientmetrics.com/projects-clients/</link>
    <description>Recent content in Projects &amp; Clients on Handbook</description>
    <generator>Hugo -- gohugo.io</generator><atom:link href="https://handbook.gradientmetrics.com/projects-clients/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Approaching Contacts</title>
      <link>https://handbook.gradientmetrics.com/projects-clients/approaching-contacts/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://handbook.gradientmetrics.com/projects-clients/approaching-contacts/</guid>
      <description>Intermediary Collaborator Random Person Vendor Potential Client Existing Client Competitor The 50/50 Call     Intermediary These are companies or people that would not necessarily use Gradient directly, but would have an interest in having us work with a connection of theirs to create value.For example: investment firms that have portfolio companies that would benefit from Gradient&amp;rsquo;s services.
Potential Objectives:
 Introduce Gradient Get introductions to their contacts  Potential Approaches:</description>
    </item>
    
    <item>
      <title>Proposal Guidelines</title>
      <link>https://handbook.gradientmetrics.com/projects-clients/proposal-guidelines/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://handbook.gradientmetrics.com/projects-clients/proposal-guidelines/</guid>
      <description>Capture and Deliver what the Client Needs Pricing Approach Preparing a Budget Set Stage for Subsequent Business Review and Approval     Capture and Deliver what the Client Needs Resist the temptation to offer a potential client more than what they need or ask for. In the long-term, Gradient will secure more business by excelling at what our clients demand of us than by jeopardizing a relationship by over-selling.</description>
    </item>
    
    <item>
      <title>Proposal Writing Workflow</title>
      <link>https://handbook.gradientmetrics.com/projects-clients/proposals/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://handbook.gradientmetrics.com/projects-clients/proposals/</guid>
      <description>Guidelines  Jira Issue Template Documents   Workflow Terms     Guidelines We typically do proposals via memo, not decks—this allows for more substantive conversation than a deck. Before telling them what we&amp;rsquo;ll do, we align with them on what they need. We don&amp;rsquo;t put pricing down until we&amp;rsquo;ve done a pricing analysis.
In an ideal world, proposal development would be split into two stages: FIRST objective and methodological alignment, THEN pricing determination.</description>
    </item>
    
    <item>
      <title>Project Startup Workflow</title>
      <link>https://handbook.gradientmetrics.com/projects-clients/project-startup-workflow/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://handbook.gradientmetrics.com/projects-clients/project-startup-workflow/</guid>
      <description>Create a Codename Create a Project in JIRA  1. Create a New Project 2. Check Screen Settings for the New Project 3. Customize the Project Description, Avatar, Etc. 4. Create a JIRA Board   Integrate into Slack Create a Google Drive Folder Set Up AI Project Folder with Materials  Create a Shared Folder Upload Materials to the Folder   Prepare Project Playbook Add Bookmarks to Slack Create a Google Group Create &amp;amp; Add a Roadmap to JIRA  Consider Releases Consider Reviews   Add Recurring Issues (If Applicable) Post Mortem Setup Pre Mortem Think About the Gradient Machine Add to Quickbooks     A Step-by-Step Guide to Setting Up New Projects</description>
    </item>
    
    <item>
      <title>Project Closeout Workflow</title>
      <link>https://handbook.gradientmetrics.com/projects-clients/project-closeout-workflow/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://handbook.gradientmetrics.com/projects-clients/project-closeout-workflow/</guid>
      <description>Research Manager Closeout  Confirm Jira contractor issues are closed out Client Debrief Archive Deliverables in Repository and Drive Clean-up Data Deletion Testimonial/Referral Request   Operations Closeout  Contractor Closeout Confirm Data-Related Actual Costs Invoice the Client Infrastructure Closeout  Jira: Remove Recurring Issues Release All Releases Jira: Move to Closed Projects Archive Slack channel   Post Mortem   Code Closeout  Clean Up Project Directory Document The Project Close Project on Github       A step-by-step guide for closing out completed projects.</description>
    </item>
    
    <item>
      <title>Contractor Effort Tracking</title>
      <link>https://handbook.gradientmetrics.com/projects-clients/contractor-effort-tracking/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://handbook.gradientmetrics.com/projects-clients/contractor-effort-tracking/</guid>
      <description>Introduction Contractor Profile Manual Issue Creation     Introduction Gradient uses metrics to determine the profitability of client projects, manage bandwidth, and evaluate effort by Gradient team members. This contractor effort tracking process was created to make sure we are including contractor effort in our performance metrics.
Contractor Profile Gradient has created a singular Contractor profile in Jira to be used to assign contractor issues and track effort in Gradient metrics.</description>
    </item>
    
  </channel>
</rss>
