And so we've arrived.
It's it's it.
This is the last day, the finale, the conclusion.
Welcome to week three.
Day five, the capstone project finale.
For the last time, let's do this.
And it's so gratifying to see us on the top right there as we embark on the last day.
And first up as as usual, a quick recap.
I will keep it quick, but we covered such important material yesterday that I'd be doing a disservice
if I didn't mention it again.
Context engineering.
It's the name of the game.
It's all about squeezing into your limited input context, everything that you need to give you the
best possible chance at the LM, generating outputs consistent with your business goal.
That's what it's about.
And we explored some of the different techniques yesterday.
And one of them of course, is thinking about subagents.
If you've got too many tools, maybe find a bunch of them that you can break off and give it to a separate
agent that is sort of delegated to perhaps using a tool.
And these were some of the points that we covered.
It's it's good both for having reusable, testable steps and also for reusing the same subagent in different
flows.
It's good for the context window, and it's easy to implement in using sub workflows.
But remember, my caveats don't just create subagents because it sounds like that's what how we would
organize humans to do it.
Be aware of the fact that more subagents you're kind of you're fixing the way the problem is solved
by organizing it into these, into these blocks, these subagent building blocks.
And that might not be the most efficient way to solve the problem.
And you might want to give your agent the autonomy to decide how it wants to go about doing it.
So be aware that you are you are limiting the creativity of your overall agent.
If you force it into different subagents and that there's there's more to be done.
Building with subagents takes more time, although it tends to be easier to test and more bulletproof.
And then the whole thing was wrapped up with just this, this slide I gave you last time on what is
it that makes a good agentic commercial solution?
And I had started with the things that are the kind of the red flags, the anti-patterns.
The first of them, once again, is what I called at the beginning of the human trap.
This this time when people tend to to just sort of come up with names of agents and that's how they
begin.
They often start a project by drawing an agent architecture rather than starting from how do I solve
this problem?
Always a always a concern for me.
And then similar is when people are very solution focused.
I need an agent to do this.
Uh, and, and then, uh, generating, building an agent whose goal it is just to generate content.
And that in of itself is the goal.
That's a, that's a warning sign for me.
Provide a business strategy.
I have an agent that makes business strategies when they haven't yet identified the core problem.
These are all quite similar, these red flags.
And they often come together.
All right.
So those are the things to watch out for.
What are the things that you want to see in an agentic solution, you want to see three things a clearly
identifiable business problem that makes sense, that resonates, that hasn't just been cooked up to
to match a solution that someone wants to build.
It really is a pain point, something concrete to be fixed.
And then along with that, a metric or multiple metrics that will allow you to evaluate whether that
business problem is solved with, ideally with with something established up front that says if we reach
this level, then we've achieved success.
And then along the way, rigorous testing to demonstrate you're meeting that criteria.
And you know that my usual go to rant that a lot of this field is about R&D and experimentation.
And so when people say, I'm not sure whether I should use this architecture or this architecture,
this approach or this approach, should I use tools or structured outputs?
The typical go to answer is look, you should try both.
Experiment.
Measure your evaluation metric with both of them and pick the one that gives you the best business outcome.
This is a very empirical experimental science, and there's no shortcut for R&D.
And there you have it in a nutshell.
That's my big takeaways for the course.
And I know probably some of you are like okay.
Yeah, we know that because you've said it five times already.
And I know.
But sometimes repetition helps and it's important to get this across.
This is this is, I think, the most common way that people go off track when they're applying, particularly
people who tend to come from a technical background, who are used to doing things the software way,
when there often is a set way of doing things.
This is something that does tend to trip people up.
And since I'm from that background, I can say with confidence that it's something that in the early
days I struggled with too.
Okay, thank you for bearing with me for that final recap.
The last recap.
You don't have to put up with it anymore.
It's time for us to go back to our capstone project and finish things off.
And the capstone project you'll remember called Amplify Your Business, something that is great that
it can be applied to your own personal work that you do to your company, to your day job, to to your
agency, to your clients.
It's so generally applicable.
It's about building a platform that can generate new business, bring in revenue.
And I'm giving you a starting point.
There's many different directions you can take it.
So the agent we started working on last time is the first of two agents, the outbound sales agent.
We we built.
We've now built all three sub agents.
A few days ago, we built the prospecting Subagent.
Then yesterday we built the Revops and SDR sub agents.
And now we need to put them together into a business development manager agent.
That's going to take advantage of these sub agents.
We're going to go and do that now.
And the first step is that the sub agents are set up to, to to have like a chat trigger or one of them
I think is just a button to trigger it.
And we need to change that so that it can be triggered by the business development manager.
So we'll go and do that and turn them into real subagents.
And then then we're going to be ready to make our manager agent and bring together this agent number
one outbound sales.
Let's go back to Nan okay.
Here I am back in and in the home overview page I'm going to flip over to the amplify project, go into
business development, bring up our SDR sub agent, the sub agent that grabs people and Pipedrive shoves
them and creates draft Gmail emails.
Okay, this is currently triggered by pressing the Execute Workflow button.
Let's get rid of that trigger instead of that.
Sorry, that's what I meant to do.
There we go.
Delete.
Now press tab to create a new trigger.
The trigger we want is this one when executed by another workflow.
And we're going to say over here input data mode.
Just accept all data.
We don't actually care.
This thing is something which is just going to kick off this process.
There we go.
Uh, and now save that, and you may remember, there's one more thing we need to do for this to work,
for it to be able to be executed by another workflow.
This SDR subagent needs to be published.
So there we go.
We publish it.
Workflow is published.
Got it done.
Uh, okay.
That's that.
That's the SDR subagent.
Now we go back here and back into business development.
It's time for us to do Revops.
So here is Revops.
It is, of course, the agent that first takes some message, turns it into structured outputs, and
then stores that in Pipedrive.
Okay, just before we do this, let me just remove this chat message received right here before we put
it in the right trigger.
I think we can make this a little bit tidier to clean it up for the fact that we are we are going going
live with this.
Let's add some stickies, which is a nice practice to make it able to be easily able to be read by other
people.
Okay.
So you remember you press the sticky button over here, we get a sticky note.
Bring this up.
We're going to it's a little bit fiddly this thing, but you get used to it after a little bit.
You bring that up, make it resize it so it fits nicely.
Let's call this, uh, vase data.
Use an agent with structured outputs.
There we go, here we go.
That's our parse data.
Sticky.
And then I'm going to have another sticky note right here.
Make it a little bit bigger.
Move it up there.
Make it even bigger.
Make it nice and flush like that.
And this is going to say.
Load data.
And this is going to say store uh, the um prospect data in Pipedrive.
There we have it.
I think that's a go.
Let's have a look at how that looks.
Yeah, that looks nice and clean now.
Very good.
Okay, now we've done that.
Housekeeping.
Let's add the trigger.
Okay, here we go.
Add the trigger.
We are not going to trigger manually.
We're going to trigger when executed by another workflow.
All right.
And now we're going to have to be a little bit more careful with this.
Let's first connect it in.
Remind ourselves what this agent does.
It has a system prompt based on the input from the user which describes a sales lead.
Okay fine.
Let's go back here.
So there should be a field in here.
And that field name should be something like sales lead description.
And this is a type string.
So that is the input schema.
Sales lead description.
Okay.
Now of course we still need to do something.
We need to update this so that it's expecting that to come in.
Right now it's expecting a chat trigger node to be coming in.
Okay, so this assumes a connected chat trigger node which is wrong.
We want to define it ourselves.
We want to have an expression and we want this to be dollar JSON dot.
And then the field that we just defined which is sales lead description.
Sales lead description is what will be passed in.
So that is hopefully now going to be exactly what it's expecting.
And then that's going to be nice.
It's going to make sense and everything is hopefully going to work okay.
What else to be done I think you know I hope you know one more thing to do.
Yes we should we should publish it, save it first and then publish.
Off it goes.
That is now workflow published.
We have everything set up properly.
Here is our very robust looking Revops sub agent waiting to be executed by another workflow.
An example of a sub agent that we've implemented using a sub workflow.
Okay, now it's time for the agent.