diff --git a/Outline/Questions for building a methodology.md b/Outline/Questions for building a methodology.md
new file mode 100644
index 0000000..e215269
--- /dev/null
+++ b/Outline/Questions for building a methodology.md	
@@ -0,0 +1,26 @@
+That sounds like a great focus area! Let’s start by exploring the foundational aspects of your methodology:
+
+### Foundational Questions
+1. **Core Principles**: What are the core principles you believe every software company should follow when implementing authentication and authorization?
+2. **Common Pitfalls**: What are the most common mistakes or oversights you’ve seen companies make in this area?
+3. **Security First**: How do you prioritize security without compromising user experience? Do you have a guiding philosophy or process for balancing these two?
+4. **Industry Standards**: Which industry standards (e.g., OAuth, SAML, JWT) do you consider essential? How do you decide which ones to use or recommend to clients?
+
+### Process-Oriented Questions
+1. **Assessment**: When you first engage with a client, how do you assess their current authentication and authorization setup? What key factors do you evaluate?
+2. **Implementation Steps**: What are the high-level steps you follow to implement a secure and scalable authentication system? Can these be broken down into phases or stages?
+3. **Customization**: How do you tailor your approach to different types of companies, whether they are startups, mid-sized companies, or large enterprises?
+4. **Tools and Technologies**: What specific tools, libraries, or technologies do you prefer for different stages of the process (e.g., identity management, access control, monitoring)?
+
+### Methodology Differentiators
+1. **Unique Approach**: What sets your methodology apart from others in the industry? Do you have a specific framework, technique, or tool that you’ve developed or refined?
+2. **Client Collaboration**: How do you work with clients throughout the process? What strategies do you use to ensure that your solutions align with their business goals and technical needs?
+3. **Adaptability**: How does your methodology adapt to the ever-changing landscape of security threats and compliance requirements?
+4. **Education and Empowerment**: How do you educate and empower your clients to maintain and evolve their authentication and authorization systems after your engagement ends?
+
+### Results and Outcomes
+1. **Success Metrics**: How do you measure the success of your authentication and authorization implementations? What metrics or KPIs do you track?
+2. **Case Studies**: Do you have any success stories or case studies that illustrate the impact of your methodology? What were the key challenges, solutions, and outcomes?
+3. **Long-Term Maintenance**: What do you recommend for ongoing maintenance and security updates? How do you ensure that your clients stay protected over time?
+
+These questions should help you start to form a comprehensive methodology that you can later refine and expand into your book and consulting work.
diff --git a/Outline/Suggested outline - Daniel Priestly.md b/Outline/Suggested outline - Daniel Priestly.md
new file mode 100644
index 0000000..d0b2e39
--- /dev/null
+++ b/Outline/Suggested outline - Daniel Priestly.md	
@@ -0,0 +1,43 @@
+1. Who is the book for?
+   List of all the things that frustrate them
+   List of all the questions they have asked
+   List of their hopes, drams, wishes outcomes, desires
+   List of all the things that have frustrated them in the past
+
+Key sections:
+
+Intro in the opening of the book, sell the reader that they should finish the book.
+What are they going to get from the book?
+What problems is it going to solve?
+What questions is it going to answer?
+What methodology is it going to reveal?
+Bonuses for the end of the book (maybe)?
+
+Distruption
+3-4 chapters that disrupt people about how they are approaching their problem wrong.
+e.g. Your best thinking for 5 years ago is your baggage today.
+e.g. your entrepenural journey is predictable and there are certain steps you can take along the way.
+
+Insights
+5 or 6 key High level ideas, sharing the new ways of thinking
+High level ideas, new frameworks, new ways of thinking of things.
+At the end of the insights section add a call to action such as a scorecard. Help them benchmark how far along the path they are.
+The CTA also helps you turn them into a warm lead.
+
+Methodology
+This should be completely unique to you. How to achieve the result.
+Share enough that they can go directionally correct and see that you know what you are talking about.
+They can feel comfortable that they can reach out to you to get further details, or use your company to get solutions
+
+Objection Handling
+Address all the reasons people would not adopt your methodology.
+People want it to be easier, but they'll have to do something for the result.
+You want to handle the objections that might come up.
+Second CTA, give them exactly what you want them to do in order to get started on the methodology.
+
+Leave people on an inspirational high
+Talk about the big picture of getting this done.
+What is the real reason that you want people to act?
+What is on the other side of the pain?
+What is on the otherside of commitment and discipline?
+