Step 3 - The PRD

[00:00 - 00:05] Step three is the PRD. PRD stands for Project Requirements Document.

[00:06 - 00:28] So when working with clients, one of the most important documents you'll get is a project-required in the segment. Because this document basically showcases exactly why we're going to build, when is it not considered done, when can I stop working, when can I deliver it to you?

[00:29 - 00:56] Because this inserts at both the client and the developer have agreed beforehand on what the developer needs to develop and what the client will get. Otherwise, you will have disagreements, you will have payment issues, while if you have the beforehand and sign, you know that, okay, we have agreed on this, I gave you exactly what we agreed upon.

[00:57 - 01:11] So now you don't have an excuse to ask for more without paying me more or just not paying me in general. So not everyone does that, but if you work with big clients and they're going to have a safe agreement, a PRD is a must.

[01:12 - 01:25] So this time the prompt is very simple, just helping generate a project requirements document. So we bested in and we waited me.

[01:26 - 01:39] So below the structure, project requirements document, for our AI therapies mobile lab. So the purpose is to provide an AI power conversation experience that mimics therapeutic dialogue.

[01:40 - 01:48] The app is intended to support and wants to run a journaling engineering projection for people who may not have access to, and they're not able to do it. So we're going to do that.

[01:49 - 01:58] And for people who may not have access to or interested in traditional therapy. Do you need a mobile app where you're trying to start the best interface powered by a vault?

[01:59 - 02:19] Say your data storage does not provide medical or crash software, that's important. That our text tank, our target users, and the extension professional machine support, you can reside in the request for therapy alternatives and training association shift connectors.

[02:20 - 02:27] This is our core features. We'll get into that later.

[02:28 - 02:33] These are secondary features. Again, we'll see more about that later.

[02:34 - 02:40] That's not ideal. I will see how to build it out by ourselves.

[02:41 - 02:51] These are some non-factual requirements which again, we can ignore for now. They are not as important, although they are.

[02:52 - 03:08] Inboard, I mean, if the response time is less than one second, or one second on the dot, is not that big of a deal for your MVP? Okay, security obviously is important.

[03:09 - 03:20] And the NNN governance should be further, essentially. So, most of it is actually very on point after all.

[03:21 - 03:31] So, I think we're my static minimus that the real okay, these are some good pointers, but again, we'll see more of that as we go on with the workflow.