Home Home Templates Services Newsletter Log In Sign Up
Coarchy Template
Description
Our mission is to Organize your Organization. We decided to create software that will allow for the articulation of the design of the organization and create requirements for running it so that the organization can run smoothly when key people are out of the office, everyone can know where they fit in the organization, know what other people are doing, and reduce conflict and duplicate work with clear roles and responsibilities.
Origin Story
Coarchy came together when Michael, David, and Guru Dharam decided to create a business using our expertise in analysis and design of business software applied to everyday organizations. Just about everything that we consume, live in, see, and do is in some part governed by an organization. Each organization has its own way of performing activities. The way people perform activities in an organization is often confusing, difficult, or flat out wrong. A series of these activities over time are processes. Processes are a great way to improve the alignment, value, scalability, and collaboration of a business, but most of the time organizations don't articulate them to get the benefits.
Vision
90 Days: Ramp up sales and marketing to 100 customers by creating a blog and messaging people, reaching out and converting prospects into customers. Maintain product by fixing bugs and improve the onboarding experience and documentation. Long term: Create software that is used by virtually every organization to articulate their processes, values, and vision. Coarchy will improve organizational drive, focus, and will change economies for the better. Coarchy will turn the current old half broken steam engine organizations into well oiled high performance engines that last 100 years while adapting to the current environment.
Statements
  • Emails are sent every day at 9am Ideal
  • marketing emails need to look decent Ideal
  • Marketing emails are sent for ~2 weeks to explain the different features of the product and how to use it. Ideal
  • Search engine optimization (SEO) Benefit
  • When giving requirements to programmers don't ask them to find problems in the code unless they recently wrote the problem. Have other people find and state the problems clearly for the programmer Ideal
  • By default, minimize the change in structure of organizations Requirement Statement
  • One person, one task, one objective, at one time Ideal
  • Focus Ideal
  • Teams with people who have the right mix of values and personalities work better together Ideal
  • Minimize the bullshit Ideal
  • One coding task, one pr, multiple commits Ideal
  • Minimize the time customers need to spend in the application (Make it feel like there is no process. It's just what you for your job) Ideal
  • Only focus on only what has great leverage to the customer Ideal
  • The more roles in a process the less efficient it is. The more processes there are the less efficient the organization is Ideal
  • At different times, the same organization will prioritize different values. In an upward market they may prioritize time, in a downward market they may prioritize efficiency Ideal
  • Everytime an organization scales, they will need to re-architect their organization Ideal
Actors
  • Admin Team – Consists of finance, legal, and hr
  • Business Person
  • Coarchy – This organization
  • Colleagues
  • Customer
  • Dev Shop Ceo
  • Employee
  • Executives
  • Founder
  • IT Consultant / Contractor
  • Lead
  • Manager
  • Marketing Director – Chief marketing officers are responsible for creating and managing an organization's brand using all marketing vehicles at their disposal. A CMO typically oversees creative functions such as advertising, public relations, social media, graphic design, digital marketing, customer relationship management through email campaigns, signage and beyond. Chief marketing officers must have a global outlook as large organizations are typically engaged in other countries. A CMO may also play a role in shaping an organization's messages to investors or other members of the general public.
  • Marketing Specialist – Marketing specialists activate an organization's various marketing plans. They take direction from senior marketing managers, directors or executives on campaigns, whether it be for advertising, social media, websites, email or other elements of the marketing mix. Marketing specialists serve functions as proofreaders, to polish the work of their department, and have duties to make sure it appears in the right place at the right time.
  • Marketing Team
  • Organization
  • Organization Member – View stories, check stuff off checklist, view stuff they have roles in. Create checklist for themselves
  • Organization Owner – Can assign actors and do anything. Creates checklist for other people. Add and Delete parties from organization. Responsible for handling checklist completion.
  • Product Director – A Product Director is an individual who oversees the development and release of products for an organization. They work with team members to ensure that products are designed and developed according to company standards. Their role is to guide other product professionals in their jobs and troubleshoot any challenges they encounter. They act as an important leading figure within the overall product team and have visibility of all levels of product development, from design to agile product delivery.
  • Product Engineer – Product Engineers typically work for organizations across industries to ensure the creation of quality products. They work closely with manufacturing professionals to effectively create products using assembly teams and manufacturing equipment. Their job is to research the best materials to use for a product and consult with other Product Engineers to develop and test prototypes. They may also be responsible for addressing product defects and using consumer feedback to refine product designs.
  • Production Engineer – Production engineers are highly skilled individuals who oversee and implement the manufacturing of products. These engineers often work with a team of product designers to ensure the manufacturing process results in optimal finished products.
  • Product Team
  • Programmer
  • Prospect
  • Sales Director – A sales director is a senior sales manager who oversees sales performance for a business. Depending on the business' size, a sales director may supervise sales managers or regional sales managers who lead sales teams. They ensure multiple sales teams maintain consistent standards and meet their sales targets. They help develop the business' sales campaigns and marketing strategies. Sales directors also approve sales projections and budgets. They deliver reports on the business' sales performance directly to the executive board.
  • Salesperson – A salesperson sells a business' products or services to customers. Salespeople may answer phones, speak with clients about questions they might have and sell products to customers directly.
  • Sales Team
  • Search Engine
  • Solution Architect
  • Story writer – Can create actors, activities, create checklist.
  • System Vendor
  • User
  • Vendor Representative
Process Stories
  1. Coarchy Top Level
    1. Marketing Team generates leads.
      1. keywords are found based off of the target market.
        1. target market can be internal teams that have business analysts who use diagramming tools for conveying information who can instead use coarchy.
        2. target market can be DevOps internal team who develop SaaS products for product and sales people that need to gather requirements for the engineering team.
        3. target market can be dev shop currently in scaling mode that need to gather requirements for their clients to define scope and provide progress of creation for requirements.
        4. target market can be startups that want to plan their business and get software to fit their business requirements (vars for startups).
      2. ads are placed on linkedin and google.
      3. the ads have a message that is a/b tested.
      4. the ads are based on a campaign for a specific target market.
      5. When prospect clicks on an add, Prospect goes to the coarchy.com website.
      6. When signing up, Prospect automatically enrolls into onboarding emails.
      7. Prospect convert into leads once the prospects sign up on coarchy.com website.
      8. conversion to sign up are tracked.
      9. After sign up, Organization automatically nurtures Leads through marketing emails.
        1. Upon sign up, Lead agrees to get sent strictly follow up emails (see: https://brandpitchapp.com/the-five-emails-every-saas-and-ecommerce-business-must-send-to-new-users/ #3).
        2. Lead gets added to a mailing list.
        3. Immediately after sign up, Lead gets sent a welcome email to setup an organization, invite users, and open the app.
        4. Immediately after sign up, Lead gets sent a mission email.
        5. If the user hasn't already created a Organization 2 days after sign up, Lead gets sent a activation email to setup an organization.
        6. If the user hasn't already invited a user 4 days after sign up, Lead gets sent a activation email to invite a user.
        7. 6 days after sign up, Lead gets sent a activation email to create a process story with activities.
        8. 8 days after sign up, Lead gets sent an activation email to create an actor.
        9. When a user is sent a promotional email, User can unsubscribe from the email.
          1. On the footer of the email, User presses an unsubscribe button.
          2. User authenticates via token in the url to the unsubscribe screen.
          3. User gets taken to the unsubscribe screen.
          4. Organization automatically find the contacts list and party based on token in url.
          5. User can unsubscribe from the contact list the email was sent to.
          6. Once the User unsubscribes, User receives a success or failure message.
          7. User can return to the original application.
        10. User may see lists of contact lists available and may subscribe or unsubscribe to them in settings.
      10. newsletters are sent every 2 weeks to explain the different features of the product and how to use it, industry insights, thought pieces etc.
        1. newsletters are sent via email.
        2. newsletters are sent via blog posts to hacker news.
      11. If user is subscribed to the newsletter, every 2 weeks, an email is sent to the user.
        1. Marketing Specialist writes an email.
        2. Marketing Specialist converts it into an html.
        3. Marketing Specialist uploads the to the server with the necessary data.
        4. Organization Owner ensures the email is setup before the 2 week date.
        5. email is sent out.
        6. User can unsubscribe from the email in the footer.
          1. On the footer of the email, User presses an unsubscribe button.
          2. User authenticates via token in the url to the unsubscribe screen.
          3. User gets taken to the unsubscribe screen.
          4. Organization automatically find the contacts list and party based on token in url.
          5. User can unsubscribe from the contact list the email was sent to.
          6. Once the User unsubscribes, User receives a success or failure message.
          7. User can return to the original application.

      13. Daily at 10am Central, Organization automatically sends emails.
        1. contact list email has wiki blog category.
        2. find contact list.
        3. look for recent wiki blog posts in the wiki blog category that haven't been posted.
        4. send the wiki blog posts as an email with an email template.
    2. Sales Team trains and implements customer.
      1. User invites other User from organization to join organization.
      2. If invited user doesn't already exist, Organization automatically creates new user account.
      3. Organization automatically assigns user to be a prospect in the sales journey.
      4. Organization automatically sends out invite email.
      5. Once invited user opens email, Organization automatically records the opening.
      6. Once User signs up through email, Organization automatically makes user a Hot Lead in the sales journey.
      7. After 30 days of User not logging in, if User is a hot lead, Organization automatically assigns the User to be a cold lead.
      8. If user logs in and is a cold lead, Organization automatically assigns the User to be a hot lead in the sales journey.
      9. Once User buys an organization credit, Organization automatically assigns the user to be a Paying Customer in the sales journey.
      10. If the User is a Paying Customer in the sales journey and (has no organization credits, or hasn't had an organization active for 30 days), Organization automatically assigns the user to be a Previously Paying Customer.
    3. Customer uses Coarchy.
      1. Organization Owner signs up to Coarchy.
      2. Organization Owner goes to Organizations screen.
      3. If there are no private organizations, Coarchy explains what an organization is, what it is for, and notifies the User that they should create an Organization either by copying an existing one or creating a new blank organization.
      4. Organization Owner create an organization with a name.

      6. Organization Owner invite Members of the Organization to join the organization.
      7. Organization Owner select an organization.

      9. If there is no Vision for the organization, Coarchy briefly explains what a Vision is and invites the User to create it (show in Home and Vision Screen).
      10. Organization Owner creates the origin story, mission, and vision.
      11. If there are no Statements in the organization, Coarchy briefly explains what an Statement is and invites the User to create some (show in Home and Statement Screen).
      12. Organization Owner creates statements.
      13. If there are no Actors in the organization, Coarchy briefly explains what an Actor is and invites the User to create some (show in Home and Actors Screen).
      14. Organization Owner create actors.
      15. If there are no Process Stories in the organization, Coarchy briefly explains what a Process Story is and invites the User to create one (show in Home and Find Process Story Screen).
      16. Organization Owner create a process story.
      17. Optionally, Organization Owner assigns parties to actor roles.
      18. If there are no Activities in the Process Story, Coarchy briefly explains what an Activity is and invites the User to create some (show in EditProcessStory and ProcessStory screens).
      19. Organization Owner create activities.
      20. Organization Owner view the process story.
      21. If there is no Products for the organization, Coarchy briefly explains what a Product is and invites the User to create some (show in Home if there is a Statement or Process Story with Activities and Products Screen).
      22. Organization Owner creates some Products.
      23. If there is no Evaluations for the organization, Coarchy briefly explains what a Evaluation is and invites the User to create some (show in Home if there is a Statement or Process Story with Activities and a Product and show in the Product Screen).
      24. Organization Owner creates the origin story, mission, and vision.

      26. Vendor Representative receives an email to evaluate a product.
      27. Vendor Representative goes to view the outstanding product evaluations.
      28. If this is the first product evaluation for the Vendor Representative and the evaluation status is not complete, Coarchy briefly explains what a product evaluations is and invites the user to complete the evaluation (in the Organizations and FindProductEvaluations screen).

      30. Organization Member create an account under the Organization Owner's organization.
      31. Organization Member select an organization.
      32. Optionally, Organization Member create actors.
      33. Optionally, Organization Member create a process story.
      34. Organization Member assigns their party to an actor role.
      35. Optionally, Organization Member create activities.
      36. Organization Member view the process story with their roles.
      37. Optionally, Organization Member view the whole process story.

      39. Organization Member tells Manager who did what.

      41. Organization Owner perform anything in the system.
      42. Story writer create process stories, actors, activities, and checklist for an actor.
      43. Organization Owner, Story writer creates a checklist.
    4. Customer pays for premium features.
      1. Customer subscribes for a product.
      2. Customer adds a payment method and related billing information.

      4. Coarchy records monthly activation usage per organization.
      5. On the first day of each month, Coarchy withdraws organization month credits from accounts for the previous month.
      6. If account doesn't have enough credits, Coarchy deactivates the organizations for that account.
      7. Coarchy generates invoices.
      8. Coarchy sends invoices to Customers.

      10. Coarchy provides Customers a statement listing outstanding invoices, partial payments and remaining amounts due.
      11. Coarchy processes Customer payment methods for invoices.
      12. If payment processing succeeds, Coarchy confirms Customer invoice status is Payment Received.
      13. If payment processing fails, Coarchy requests updated payment information from the Customer.
      14. When Customer updates payment information, Coarchy processes payment again.
      15. If the Customer fails to pay, Coarchy restricts the Customer’s account from using subscription products.

      17. If Customer is unsatisfied with subscription products, Customer submits a dispute to Coarchy.
      18. Coarchy gathers dispute information from Customer.
      19. Coarchy reviews the dispute.
      20. Coarchy may adjust or cancel invoices.
    5. Product Team develops product.
      1. Product Director creates and refines a world class product.
      2. Sales Director creates and refines an upsell techniques to increase customer lifetime value with the product.
      3. Sales Director creates and refines a referral program.
      4. Marketing Director, Product Director, Sales Director communicate the overall requirements to the Product Engineer.
      5. Product Engineer creates a design of the product.
      6. When Marketing Director, Product Director, and Sales Director approve the design, Programmer sends the design to the Production Engineer.
      7. Programmer creates the product for the customer.       
        No Activities
      8. Production Engineer packages the product.
      9. Production Engineer ships the product to the Customer.
      10. Customer uses the product.
        1. User adds value statement tag (dialog with name and submit on top of screen in actions buttons).
        2. Organization automatically limits tag names to letters and digits similar to social media platform hashtags (use regex in service parameter definitions directly called in the transition).
        3. User associates zero to many value statement tag with a value statement (multi select drop-down widget on existing form-list in ValueStatements screen).

        5. User connects an activity to a value statement (in a form single in a dialog in the valuestatement screen).
        6. User removes activity from a value statement (with a delete trash can in a form list in the activity dialog in the valuesstatement screen).
        7. User view activities attached to a valuestatement (in a form-list in the activity dialog in the valuestatement screen).

        9. keep the dialogue open on submit with see DefaultScreenMacros line 185 _openDialog.
        10. specify the dialogue id in the parameters to open the dynamic dialogue.
        11. Pass a parameter _openDialog to the dynamic dialogue id in the form for when they get submitted.
        12. see listentryindex parameter for the _openDialog parameter which could be ${id}_${listentryindex}.

        14. create entity ValueStatementTag with a tagId, name, organizationId.
        15. create ValueStatementAssoc entity with a tagId, valueStatementId, and organizationId.
        16. filter organizationId per activeOrgId.

      11. Programmer ensures that all data changes are added to the clone organization service.
      12. Salesperson answers customer questions.
      13. Salesperson addresses complaints.
      14. Salesperson upsells customer.
      15. Salesperson invites customer to send referrals.
    6. Product Team keeps track of important information for analysis.
      1. Coarchy logs different types of messages.
      2. Coarchy keeps track of most common error messages.
      3. Coarchy keeps track of how long the pages of the application are used.
      4. Coarchy keeps track of goals like Users, Organizations, Process Stories, Actors, and Activities created.
      5. As Users use the System, Coarchy allows Users to send feedback with additional information included in the feedback message.
    7. Admin Team runs organization smoothly.
      1. set clear business KPIs.
      2. Manager evaluates recruits.
      3. creates recruitment test.
      4. Manager recruits employees.
      5. If employee needs training, trains employees.
      6. evaluates employees.
      7. If employee underperforms KPI expectations, terminate employees relationship.
      8. If employee exceeded KPI expectations, rewards employees.
      9. If employee exceeded KPI expectations and a higher level actor position is open, promotes employees.
      10. Every month, Manager one on one meetings.
      11. prepares agreements.
      12. negotiates agreements.
      13. distributes agreements.
      14. provides legal counsel for business actions.
      15. handles legal and compliance matters.
      16. pays employees.
      17. accounts for financial transactions.
      18. creates financial reports.
      19. forecast financial activity from marketing lead potential and sales potential.
      20. pays for internally used products and services.
      21. recruit employees.
      22. creates budget.

  2. Coarchy keeps track of important information for analysis
    1. Coarchy logs different types of messages.
    2. Coarchy keeps track of most common error messages.
    3. Coarchy keeps track of how long the pages of the application are used.
    4. Coarchy keeps track of goals like Users, Organizations, Process Stories, Actors, and Activities created.
    5. As Users use the System, Coarchy allows Users to send feedback with additional information included in the feedback message.

  3. Customer hears about Coarchy from a friend, colleague, or acquaintance.

  4. Organization Manager , Story writer creates a checklist
    1. choose a process story.
    2. specifies a name that is optionally a variation on the process story name.
    3. If a checklist should be created for each user instead of a single checklist for all users, specifies a checklist should be created for each instead of creating a single checklist.
    4. assigns user(s) to actors in the story based on actor role assignments already recorded.
    5. If a process should be completed on a schedule, specifies the schedule parameters (first day of each week, daily monday to friday, first day of the month).
    6. automatically assigns each task to user(s) based on the actor for the activity in the story and the users selected for each actor for this checklist.
    7. automatically creates a checklist with tasks for each activity in the process story.

  5. What Coarchy could be
    1. saas business that provides meaning to the employees and removes the bullshit that kills drive and productivity in your employees and makes it so that you only pursue your mission and don't waste time on unnecessary tasks. do what matters, change the world.


    2. take in a whole bunch of text and see what someone believes and values.
    3. take a whole bunch of text and see what some believes when talking with other people.
    4. Manager can see what people believe and value in the organization.
    5. Employee can see the impact of what their work is having on the world.
    6. take a whole bunch of tasks of one person or many and see what is the end effect of them at a project level.
    7. take a group of projects and see what the end effect of them is at goals.
    8. take a group of goals and figure out what the organization's values are.
    9. take a group of values and figure out what the mission is.
    10. compare the actual mission to what is actually going on in the company.
    11. take a whole bunch of tasks in the company and find the processes that the company executes.
    12. fill that data in coarchy.
    13. values can be determined by how you promote your employees, provide bonuses, or give praise. They are things that are valued so valuables are traded for them.


    14. In a job survey like https://newpossible.io/resources/what-workers-want-2023-findings, Manager realizes that 20% of their employees are more likely to stay if employees find their work more fulfilling and engaging work.
    15. In a job survey like https://newpossible.io/resources/what-workers-want-2023-findings, Manager realizes that 23% of employees are likely to leave due to unhealthy culture like unpredictability, bad communication, lack of structure / stability / power, ignored, politics, and bureaucracy.
    16. In a job survey like https://newpossible.io/resources/what-workers-want-2023-findings, Manager realizes that 22% of their employees are more likely to leave because of poor leadership.
    17. Manager searches for a solution and finds coarchy.
    18. Manager realizes that Employees need 1 hour for first time setup and then 15 minutes of time each day for a x% amount of improvement in less likely to leave company and y% amount more likely to stay at the company and a z% better culture fostered in the company.
    19. Manager performs an internal job survey about likeliness to leave, likeliness to stay, and job fulfillment / purpose.
    20. Manager measures kpis before and monitors them throughout the process.
    21. Manager implements coarchy for 1 month.
      1. document how benefits are implemented with examples processes in the software.

      3. document activities and actors that are responsible for them.
      4. assign employees to actor roles.
      5. Employee review their assigned roles and the descriptions of them and the business activities that are associated with them that they are responsible for.
    22. Manager performs a follow up job survey and sees an improvement.
    23. Manager buys coarchy for tons of money and saves tons of money for their organization.
    24. Manager shares the good story with the executives at the organization.
    25. Executives implement coarchy across the organization.




    26. Employee completes tasks every day and doesn't clearly know what impact they have or what they're for.
    27. Employee doesn't have enough information about the tasks that they're doing and the goals and mission of the company to make good prioritization decisions.
    28. Coarchy, Story writer takes tasks and creates processes from them and records them.
    29. Coarchy, Story writer connect processes to tasks.
    30. Employee now understands how their work impacts other people in the organization, and understands how the organization functions.
    31. Manager has their decisions articulated so that they don't have to micro-manage the employees.
    32. Employee understands their role and responsibilities within the organization.


    33. Coarchy, Executives, Manager records value statements that can be determined by how you promote your employees, provide bonuses, or give praise / what do you admire about others.
    34. Coarchy, Executives, Manager connects value statements to process stories / activities.
    35. Employee understands how to gain bonuses, how to act at work, and is more likely to enjoy because there is good communication about what needs to happen to be promoted, get bonuses, or get praise.


    36. Coarchy, Executives, Founder record what the vision story is including the origin story, mission, high level outcomes, high level goals, and vision.
    37. Coarchy, Executives, Founder connect the vision story to value statements.
    38. Employee understands how the work they do impacts the world and customers.
    39. Employee finds their work fulfilling and engaging.
    40. Organization is now integrated because they know what is going on at different levels of analysis, how they operate internally (culture) and how they impact the world (mission).
    41. Organization is more productive with objectives, responsibilities, and accountability clearly stated with Employees that make better decisions and find their lives more meaningful and fulfilling.

  6. Manager implements coarchy for 1 month
    1. document how benefits are implemented with examples processes in the software.


    2. document activities and actors that are responsible for them.
    3. assign employees to actor roles.
    4. Employee review their assigned roles and the descriptions of them and the business activities that are associated with them that they are responsible for.

  7. Customer pays for product
    1. Customer subscribes for a product.
    2. Customer adds a payment method and related billing information.


    3. Coarchy records monthly activation usage per organization.
    4. On the first day of each month, Coarchy withdraws organization month credits from accounts for the previous month.
    5. If account doesn't have enough credits, Coarchy deactivates the organizations for that account.
    6. Coarchy generates invoices.
    7. Coarchy sends invoices to Customers.


    8. Coarchy provides Customers a statement listing outstanding invoices, partial payments and remaining amounts due.
    9. Coarchy processes Customer payment methods for invoices.
    10. If payment processing succeeds, Coarchy confirms Customer invoice status is Payment Received.
    11. If payment processing fails, Coarchy requests updated payment information from the Customer.
    12. When Customer updates payment information, Coarchy processes payment again.
    13. If the Customer fails to pay, Coarchy restricts the Customer’s account from using subscription products.


    14. If Customer is unsatisfied with subscription products, Customer submits a dispute to Coarchy.
    15. Coarchy gathers dispute information from Customer.
    16. Coarchy reviews the dispute.
    17. Coarchy may adjust or cancel invoices.

  8. Product Story
    1. Customer (as an organization) has many activities they do.
    2. Customer each activity needs one role to go with it.
    3. Customer each role belongs to an organizational unit.
    4. Customer each activity has other activities that are done at around the same time in sequence (these create a process story).
    5. Customer in each activity the actor is transforming assets into another asset to a greater value.
    6. Customer eventually the assets get assembled into a product.
    7. Customer the product is then sold to the customer in exchange for money.

  9. Programmer creates deploys new features

  10. Marketing
    1. keywords are found based off of the target market.
      1. target market can be internal teams that have business analysts who use diagramming tools for conveying information who can instead use coarchy.
      2. target market can be DevOps internal team who develop SaaS products for product and sales people that need to gather requirements for the engineering team.
      3. target market can be dev shop currently in scaling mode that need to gather requirements for their clients to define scope and provide progress of creation for requirements.
      4. target market can be startups that want to plan their business and get software to fit their business requirements (vars for startups).
    2. ads are placed on linkedin and google.
    3. the ads have a message that is a/b tested.
    4. the ads are based on a campaign for a specific target market.
    5. When prospect clicks on an add, Prospect goes to the coarchy.com website.
    6. When signing up, Prospect automatically enrolls into onboarding emails.
    7. Prospect convert into leads once the prospects sign up on coarchy.com website.
    8. conversion to sign up are tracked.
    9. After sign up, Organization automatically nurtures Leads through marketing emails.
      1. Upon sign up, Lead agrees to get sent strictly follow up emails (see: https://brandpitchapp.com/the-five-emails-every-saas-and-ecommerce-business-must-send-to-new-users/ #3).
      2. Lead gets added to a mailing list.
      3. Immediately after sign up, Lead gets sent a welcome email to setup an organization, invite users, and open the app.
      4. Immediately after sign up, Lead gets sent a mission email.
      5. If the user hasn't already created a Organization 2 days after sign up, Lead gets sent a activation email to setup an organization.
      6. If the user hasn't already invited a user 4 days after sign up, Lead gets sent a activation email to invite a user.
      7. 6 days after sign up, Lead gets sent a activation email to create a process story with activities.
      8. 8 days after sign up, Lead gets sent an activation email to create an actor.
      9. When a user is sent a promotional email, User can unsubscribe from the email.
        1. On the footer of the email, User presses an unsubscribe button.
        2. User authenticates via token in the url to the unsubscribe screen.
        3. User gets taken to the unsubscribe screen.
        4. Organization automatically find the contacts list and party based on token in url.
        5. User can unsubscribe from the contact list the email was sent to.
        6. Once the User unsubscribes, User receives a success or failure message.
        7. User can return to the original application.
      10. User may see lists of contact lists available and may subscribe or unsubscribe to them in settings.
    10. newsletters are sent every 2 weeks to explain the different features of the product and how to use it, industry insights, thought pieces etc.
      1. newsletters are sent via email.
      2. newsletters are sent via blog posts to hacker news.
    11. If user is subscribed to the newsletter, every 2 weeks, an email is sent to the user.
      1. Marketing Specialist writes an email.
      2. Marketing Specialist converts it into an html.
      3. Marketing Specialist uploads the to the server with the necessary data.
      4. Organization Owner ensures the email is setup before the 2 week date.
      5. email is sent out.
      6. User can unsubscribe from the email in the footer.
        1. On the footer of the email, User presses an unsubscribe button.
        2. User authenticates via token in the url to the unsubscribe screen.
        3. User gets taken to the unsubscribe screen.
        4. Organization automatically find the contacts list and party based on token in url.
        5. User can unsubscribe from the contact list the email was sent to.
        6. Once the User unsubscribes, User receives a success or failure message.
        7. User can return to the original application.
    12. Daily at 10am Central, Organization automatically sends emails.
      1. contact list email has wiki blog category.
      2. find contact list.
      3. look for recent wiki blog posts in the wiki blog category that haven't been posted.
      4. send the wiki blog posts as an email with an email template.

  11. Sales
    1. User invites other User from organization to join organization.
    2. If invited user doesn't already exist, Organization automatically creates new user account.
    3. Organization automatically assigns user to be a prospect in the sales journey.
    4. Organization automatically sends out invite email.
    5. Once invited user opens email, Organization automatically records the opening.
    6. Once User signs up through email, Organization automatically makes user a Hot Lead in the sales journey.
    7. After 30 days of User not logging in, if User is a hot lead, Organization automatically assigns the User to be a cold lead.
    8. If user logs in and is a cold lead, Organization automatically assigns the User to be a hot lead in the sales journey.
    9. Once User buys an organization credit, Organization automatically assigns the user to be a Paying Customer in the sales journey.
    10. If the User is a Paying Customer in the sales journey and (has no organization credits, or hasn't had an organization active for 30 days), Organization automatically assigns the user to be a Previously Paying Customer.

  12. Product
    1. Product Director creates and refines a world class product.
    2. Sales Director creates and refines an upsell techniques to increase customer lifetime value with the product.
    3. Sales Director creates and refines a referral program.
    4. Marketing Director, Product Director, Sales Director communicate the overall requirements to the Product Engineer.
    5. Product Engineer creates a design of the product.
    6. When Marketing Director, Product Director, and Sales Director approve the design, Programmer sends the design to the Production Engineer.
    7. Programmer creates the product for the customer.     
      No Activities
    8. Production Engineer packages the product.
    9. Production Engineer ships the product to the Customer.
    10. Customer uses the product.
      1. User adds value statement tag (dialog with name and submit on top of screen in actions buttons).
      2. Organization automatically limits tag names to letters and digits similar to social media platform hashtags (use regex in service parameter definitions directly called in the transition).
      3. User associates zero to many value statement tag with a value statement (multi select drop-down widget on existing form-list in ValueStatements screen).

      5. User connects an activity to a value statement (in a form single in a dialog in the valuestatement screen).
      6. User removes activity from a value statement (with a delete trash can in a form list in the activity dialog in the valuesstatement screen).
      7. User view activities attached to a valuestatement (in a form-list in the activity dialog in the valuestatement screen).

      9. keep the dialogue open on submit with see DefaultScreenMacros line 185 _openDialog.
      10. specify the dialogue id in the parameters to open the dynamic dialogue.
      11. Pass a parameter _openDialog to the dynamic dialogue id in the form for when they get submitted.
      12. see listentryindex parameter for the _openDialog parameter which could be ${id}_${listentryindex}.

      14. create entity ValueStatementTag with a tagId, name, organizationId.
      15. create ValueStatementAssoc entity with a tagId, valueStatementId, and organizationId.
      16. filter organizationId per activeOrgId.

    11. Programmer ensures that all data changes are added to the clone organization service.
    12. Salesperson answers customer questions.
    13. Salesperson addresses complaints.
    14. Salesperson upsells customer.
    15. Salesperson invites customer to send referrals.

  13. Customer uses product
    1. Organization Owner signs up to Coarchy.
    2. Organization Owner goes to Organizations screen.
    3. If there are no private organizations, Coarchy explains what an organization is, what it is for, and notifies the User that they should create an Organization either by copying an existing one or creating a new blank organization.
    4. Organization Owner create an organization with a name.


    5. Organization Owner invite Members of the Organization to join the organization.
    6. Organization Owner select an organization.


    7. If there is no Vision for the organization, Coarchy briefly explains what a Vision is and invites the User to create it (show in Home and Vision Screen).
    8. Organization Owner creates the origin story, mission, and vision.
    9. If there are no Statements in the organization, Coarchy briefly explains what an Statement is and invites the User to create some (show in Home and Statement Screen).
    10. Organization Owner creates statements.
    11. If there are no Actors in the organization, Coarchy briefly explains what an Actor is and invites the User to create some (show in Home and Actors Screen).
    12. Organization Owner create actors.
    13. If there are no Process Stories in the organization, Coarchy briefly explains what a Process Story is and invites the User to create one (show in Home and Find Process Story Screen).
    14. Organization Owner create a process story.
    15. Optionally, Organization Owner assigns parties to actor roles.
    16. If there are no Activities in the Process Story, Coarchy briefly explains what an Activity is and invites the User to create some (show in EditProcessStory and ProcessStory screens).
    17. Organization Owner create activities.
    18. Organization Owner view the process story.
    19. If there is no Products for the organization, Coarchy briefly explains what a Product is and invites the User to create some (show in Home if there is a Statement or Process Story with Activities and Products Screen).
    20. Organization Owner creates some Products.
    21. If there is no Evaluations for the organization, Coarchy briefly explains what a Evaluation is and invites the User to create some (show in Home if there is a Statement or Process Story with Activities and a Product and show in the Product Screen).
    22. Organization Owner creates the origin story, mission, and vision.


    23. Vendor Representative receives an email to evaluate a product.
    24. Vendor Representative goes to view the outstanding product evaluations.
    25. If this is the first product evaluation for the Vendor Representative and the evaluation status is not complete, Coarchy briefly explains what a product evaluations is and invites the user to complete the evaluation (in the Organizations and FindProductEvaluations screen).


    26. Organization Member create an account under the Organization Owner's organization.
    27. Organization Member select an organization.
    28. Optionally, Organization Member create actors.
    29. Optionally, Organization Member create a process story.
    30. Organization Member assigns their party to an actor role.
    31. Optionally, Organization Member create activities.
    32. Organization Member view the process story with their roles.
    33. Optionally, Organization Member view the whole process story.


    34. Organization Member tells Manager who did what.


    35. Organization Owner perform anything in the system.
    36. Story writer create process stories, actors, activities, and checklist for an actor.
    37. Organization Owner, Story writer creates a checklist.

  14. Admin Team runs organization smoothly
    1. set clear business KPIs.
    2. Manager evaluates recruits.
    3. creates recruitment test.
    4. Manager recruits employees.
    5. If employee needs training, trains employees.
    6. evaluates employees.
    7. If employee underperforms KPI expectations, terminate employees relationship.
    8. If employee exceeded KPI expectations, rewards employees.
    9. If employee exceeded KPI expectations and a higher level actor position is open, promotes employees.
    10. Every month, Manager one on one meetings.
    11. prepares agreements.
    12. negotiates agreements.
    13. distributes agreements.
    14. provides legal counsel for business actions.
    15. handles legal and compliance matters.
    16. pays employees.
    17. accounts for financial transactions.
    18. creates financial reports.
    19. forecast financial activity from marketing lead potential and sales potential.
    20. pays for internally used products and services.
    21. recruit employees.
    22. creates budget.

  15. Marketing Director creates a target market with personas
    1. identifies problems that the team can solve.
    2. identify stakeholders in the organizations.
    3. create a strategy for targeting the stakeholders through media.

  16. Marketing Specialist execute the plan by putting the right message to the right people through the right media at the right time

  17. Marketing Director defines the media to used to reach the target market
    1. finds prospects through mico campaigns.

  18. Marketing Director tailors a message to target market
    1. creates a list of best guesses of a message based on the target market.
    2. uses the language of the target market.
    3. uses a micro campaign media tools to test which message works best.
    4. finds the best message.
    5. proves that the best message works on a larger audience.
    6. continues to test potential messages.

  19. after sign up, Lead are nurtured through marketing emails
    1. Upon sign up, Lead agrees to get sent strictly follow up emails (see: https://brandpitchapp.com/the-five-emails-every-saas-and-ecommerce-business-must-send-to-new-users/ #3).
    2. Lead gets added to a mailing list.
    3. Immediately after sign up, Lead gets sent a welcome email to setup an organization, invite users, and open the app.
    4. Immediately after sign up, Lead gets sent a mission email.
    5. If the user hasn't already created a Organization 2 days after sign up, Lead gets sent a activation email to setup an organization.
    6. If the user hasn't already invited a user 4 days after sign up, Lead gets sent a activation email to invite a user.
    7. 6 days after sign up, Lead gets sent a activation email to create a process story with activities.
    8. 8 days after sign up, Lead gets sent an activation email to create an actor.
    9. When a user is sent a promotional email, User can unsubscribe from the email.
      1. On the footer of the email, User presses an unsubscribe button.
      2. User authenticates via token in the url to the unsubscribe screen.
      3. User gets taken to the unsubscribe screen.
      4. Organization automatically find the contacts list and party based on token in url.
      5. User can unsubscribe from the contact list the email was sent to.
      6. Once the User unsubscribes, User receives a success or failure message.
      7. User can return to the original application.
    10. User may see lists of contact lists available and may subscribe or unsubscribe to them in settings.

  20. When a user is sent a promotional email, User can unsubscribe from the email
    1. On the footer of the email, User presses an unsubscribe button.
    2. User authenticates via token in the url to the unsubscribe screen.
    3. User gets taken to the unsubscribe screen.
    4. Organization automatically find the contacts list and party based on token in url.
    5. User can unsubscribe from the contact list the email was sent to.
    6. Once the User unsubscribes, User receives a success or failure message.
    7. User can return to the original application.

  21. When a user is sent a promotional email, User can unsubscribe from the email
    1. On the footer of the email, User presses an unsubscribe button.
    2. User authenticates via token in the url to the unsubscribe screen.
    3. User gets taken to the unsubscribe screen.
    4. Organization automatically find the contacts list and party based on token in url.
    5. User can unsubscribe from the contact list the email was sent to.
    6. Once the User unsubscribes, User receives a success or failure message.
    7. User can return to the original application.

  22. If user is subscribed to the newsletter, every 2 weeks, an email is sent to the user
    1. Marketing Specialist writes an email.
    2. Marketing Specialist converts it into an html.
    3. Marketing Specialist uploads the to the server with the necessary data.
    4. Organization Owner ensures the email is setup before the 2 week date.
    5. email is sent out.
    6. User can unsubscribe from the email in the footer.
      1. On the footer of the email, User presses an unsubscribe button.
      2. User authenticates via token in the url to the unsubscribe screen.
      3. User gets taken to the unsubscribe screen.
      4. Organization automatically find the contacts list and party based on token in url.
      5. User can unsubscribe from the contact list the email was sent to.
      6. Once the User unsubscribes, User receives a success or failure message.
      7. User can return to the original application.

  23. Marketing (Old)
    1. Marketing Director performs a bit of market research.
      1. identifies problems that the team can solve.
      2. identify stakeholders in the organizations.
      3. create a strategy for targeting the stakeholders through media.
    2. Marketing Director creates a target market.
    3. Marketing Director tailors a message to target market.
      1. finds prospects through mico campaigns.
    4. Marketing Director defines the media to used based on message and target market.
    5. Marketing Director communicates the plan to the Marketing Specialists.
    6. Marketing Specialist execute the plan by putting the right message to the right people through the right media at the right time.     
      No Activities
    7. Customer hears about Coarchy from a friend, colleague, or acquaintance.
    8. Marketing Director gets feedback from the Marketing Specialist.
    9. Identifies people and organizations that have problems the team can solve.
    10. Marketing Director changes the marketing plan based on feedback.
    11. Prospect finds out more information about Coarchy through Coarchy’s story, marketing messages, and product offering.
    12. Marketing Specialist creates leads for the Sales team.

  24. keywords are found based off of the target market
    1. target market can be internal teams that have business analysts who use diagramming tools for conveying information who can instead use coarchy.
    2. target market can be DevOps internal team who develop SaaS products for product and sales people that need to gather requirements for the engineering team.
    3. target market can be dev shop currently in scaling mode that need to gather requirements for their clients to define scope and provide progress of creation for requirements.
    4. target market can be startups that want to plan their business and get software to fit their business requirements (vars for startups).

  25. newsletters are sent every 2 weeks to explain the different features of the product and how to use it, industry insights, thought pieces etc
    1. newsletters are sent via email.
    2. newsletters are sent via blog posts to hacker news.

  26. Sales (Old)
    1. Organization Owner enter information to sign up for Coarchy.
    2. Sales Director creates and refines a lead captures system.
    3. Sales Director creates and refines a lead nurturing system.
    4. Sales Director creates and refines a sales conversion strategy.
    5. Sales Director communicates the lead capture and nurturing system and sales strategy to the Salesperson.
    6. Salesperson captures leads.
    7. Salesperson nurtures leads.
    8. Salesperson converts leads to customers.
    9. Customer places an order for products.
    10. forecast sales potential based on marketing lead potential.

  27. Daily at 10am Central, Organization automatically sends emails
    1. contact list email has wiki blog category.
    2. find contact list.
    3. look for recent wiki blog posts in the wiki blog category that haven't been posted.
    4. send the wiki blog posts as an email with an email template.

  28. Programmer creates the product for the customer

  29. Customer uses the product
    1. User adds value statement tag (dialog with name and submit on top of screen in actions buttons).
    2. Organization automatically limits tag names to letters and digits similar to social media platform hashtags (use regex in service parameter definitions directly called in the transition).
    3. User associates zero to many value statement tag with a value statement (multi select drop-down widget on existing form-list in ValueStatements screen).


    4. User connects an activity to a value statement (in a form single in a dialog in the valuestatement screen).
    5. User removes activity from a value statement (with a delete trash can in a form list in the activity dialog in the valuesstatement screen).
    6. User view activities attached to a valuestatement (in a form-list in the activity dialog in the valuestatement screen).


    7. keep the dialogue open on submit with see DefaultScreenMacros line 185 _openDialog.
    8. specify the dialogue id in the parameters to open the dynamic dialogue.
    9. Pass a parameter _openDialog to the dynamic dialogue id in the form for when they get submitted.
    10. see listentryindex parameter for the _openDialog parameter which could be ${id}_${listentryindex}.


    11. create entity ValueStatementTag with a tagId, name, organizationId.
    12. create ValueStatementAssoc entity with a tagId, valueStatementId, and organizationId.
    13. filter organizationId per activeOrgId.



  30. Request for Information
    1. Story writer writes statements and process stories to be used as requirements for system evaluation.
    2. Organization Member adds software products to be evaluated.
      1. (new screen called Products visible in menu).
      2. If Organization Member has premium, Organization Member sees list of products (form-list of product data).
      3. If Organization Member has premium, Organization Member adds software product (product with product name and optional description filtered by organizationId).
      4. If Organization member doesn't have premium, Organization Member can still see the forms and form-lists, but they are disabled.
      5. (add System and unlimited Systems to the pricing for premium).
    3. Organization Owner sends request for proposal/information invitations to vendors for each product by selecting a organization, product, and entering an email address for the product representative.
      1. Organization Owner invites.
    4. System Vendor activates their account as a vendor for a particular product in a particular organization.
    5. System Vendor records responses to each statement and each activity with a implementation status, optionally a rating (gap defaults to 1, overlap defaults to 9, and partial overlap defaults to 5), and notes.
    6. Organization Member does internal review of system for each statement and each activity with an internal implementation status, optionally an internal rating (gap defaults to 1, overlap defaults to 9, and partial overlap defaults to 5), and internal notes.
    7. Coarchy summarizes the reviews with system name, vendor rating total, internal rating total, vendor and internal counts of gap, overlap, and partial overlap (table with 9 columns).
    8. Organization Member views report with a row for each statement or activity and each system and each vendor or internal response (columns will be activity / statement, system name, vendor / internal flag, implementation status, rating, notes).

  31. Organization Member adds software products to be evaluated
    1. (new screen called Products visible in menu).
    2. If Organization Member has premium, Organization Member sees list of products (form-list of product data).
    3. If Organization Member has premium, Organization Member adds software product (product with product name and optional description filtered by organizationId).
    4. If Organization member doesn't have premium, Organization Member can still see the forms and form-lists, but they are disabled.
    5. (add System and unlimited Systems to the pricing for premium).

  32. Organization Owner sends request for proposal/information invitations to vendors for each system
    1. Organization Owner invites.

  33. Template Catalog
    1. Search Engine visits sitemap.xml and links on the website to a template organization list page and individual template organization pages.
    2. Lead searches on a public search engine for business process templates or organization templates.
    3. Lead finds coarchy templates in the results.
    4. Asdf, asdf.
    5. Asdf, Lead asdf.
    6. Asdf, asdf.
    7. Lead views content for the template in a page.
      1. Lead views process story.
    8. If Lead goes to the template organization list, Lead views content for a template organization list (name in h2, origin story, mission, vision).
    9. If Lead goes to the template organization detail screen, Lead views content for a template organization detail (name [h1], list origin story, mission, vision [small description], statements, actors, process stories, products) (each section has an anchor and a anchor menu widget to the side on desktop and a menu in the header on mobile like https://v1.quasar.dev/vue-components/bar#frameless-electron-window).
    10. Lead clicks CTA to use the template for their organization.
    11. Lead sign up or logs in (enters in their organization name to create an organization) (passes through the organizationId).
    12. Lead goes directly to the coarchy application (activeOrgId set to the just created organization).

  34. Lead view content for the template in a page
    1. Lead views process story.

Origin Story Description Vision Actors Statements Process Stories 1. Coarchy Top Level 2. Coarchy keeps track of important information for analysis 3. Customer hears about Coarchy from a friend, colleague, or acquaintance. 4. Organization Manager , Story writer creates a checklist 5. What Coarchy could be 6. Manager implements coarchy for 1 month 7. Customer pays for product 8. Product Story 9. Programmer creates deploys new features 10. Marketing 11. Sales 12. Product 13. Customer uses product 14. Admin Team runs organization smoothly 15. Marketing Director creates a target market with personas 16. Marketing Specialist execute the plan by putting the right message to the right people through the right media at the right time 17. Marketing Director defines the media to used to reach the target market 18. Marketing Director tailors a message to target market 19. after sign up, Lead are nurtured through marketing emails 20. When a user is sent a promotional email, User can unsubscribe from the email 21. When a user is sent a promotional email, User can unsubscribe from the email 22. If user is subscribed to the newsletter, every 2 weeks, an email is sent to the user 23. Marketing (Old) 24. keywords are found based off of the target market 25. newsletters are sent every 2 weeks to explain the different features of the product and how to use it, industry insights, thought pieces etc 26. Sales (Old) 27. Daily at 10am Central, Organization automatically sends emails 28. Programmer creates the product for the customer 29. Customer uses the product 30. Request for Information 31. Organization Member adds software products to be evaluated 32. Organization Owner sends request for proposal/information invitations to vendors for each system 33. Template Catalog 34. Lead view content for the template in a page
Origin Story Description Vision Actors Statements Process Stories 1. Coarchy Top Level 2. Coarchy keeps track of important information for analysis 3. Customer hears about Coarchy from a friend, colleague, or acquaintance. 4. Organization Manager , Story writer creates a checklist 5. What Coarchy could be 6. Manager implements coarchy for 1 month 7. Customer pays for product 8. Product Story 9. Programmer creates deploys new features 10. Marketing 11. Sales 12. Product 13. Customer uses product 14. Admin Team runs organization smoothly 15. Marketing Director creates a target market with personas 16. Marketing Specialist execute the plan by putting the right message to the right people through the right media at the right time 17. Marketing Director defines the media to used to reach the target market 18. Marketing Director tailors a message to target market 19. after sign up, Lead are nurtured through marketing emails 20. When a user is sent a promotional email, User can unsubscribe from the email 21. When a user is sent a promotional email, User can unsubscribe from the email 22. If user is subscribed to the newsletter, every 2 weeks, an email is sent to the user 23. Marketing (Old) 24. keywords are found based off of the target market 25. newsletters are sent every 2 weeks to explain the different features of the product and how to use it, industry insights, thought pieces etc 26. Sales (Old) 27. Daily at 10am Central, Organization automatically sends emails 28. Programmer creates the product for the customer 29. Customer uses the product 30. Request for Information 31. Organization Member adds software products to be evaluated 32. Organization Owner sends request for proposal/information invitations to vendors for each system 33. Template Catalog 34. Lead view content for the template in a page