WEBVTT

1
00:00:00.170 --> 00:00:02.080
A project lands on your desk.

2
00:00:02.620 --> 00:00:05.710
Is it right for your business, and what
should your team do next?

3
00:00:06.170 --> 00:00:08.340
Let's work through that in EM3A.

4
00:00:09.170 --> 00:00:10.700
Already have a project list?

5
00:00:11.270 --> 00:00:14.010
Bring in the spreadsheet, check the
fields, and import it.

6
00:00:16.470 --> 00:00:20.110
Now we'll use an existing project: Arrow
Valley Solar.

7
00:00:21.170 --> 00:00:24.610
Your products and target sectors give the
scoring a starting point.

8
00:00:26.270 --> 00:00:29.950
Here, business relevance is eleven; timing
is eighty-five.

9
00:00:30.770 --> 00:00:34.380
The Spec Influence Window looks open, but
the business fit is weak.

10
00:00:35.170 --> 00:00:37.470
Both matter before you commit your team.

11
00:00:39.170 --> 00:00:40.910
Now let's prepare a Meeting Brief.

12
00:00:42.270 --> 00:00:45.690
The organisations involved, the milestones
and the questions worth asking

13
00:00:45.690 --> 00:00:47.400
are gathered into a draft.

14
00:00:49.470 --> 00:00:51.425
You can see what you're working with

15
00:00:51.425 --> 00:00:53.100
and open the underlying project evidence.

16
00:00:57.220 --> 00:00:59.640
In Project Chat, you can question the
answer.

17
00:01:00.770 --> 00:01:04.920
This follow-up asks it to separate missing
information from confirmed absence.

18
00:01:07.070 --> 00:01:11.737
The reply keeps its sources and gives us a
specific next step:

19
00:01:11.737 --> 00:01:14.070
watch for the formal consultation
documents.

20
00:01:18.170 --> 00:01:20.630
Company research adds account context,
too.

21
00:01:21.470 --> 00:01:24.145
Here we can find Island Green Power,

22
00:01:24.145 --> 00:01:26.820
the researched developer behind Arrow
Valley Solar.

23
00:01:27.370 --> 00:01:30.960
Signal Nexus keeps that project and
company context connected.

24
00:01:32.170 --> 00:01:36.395
If we need more background, contact
research suggests a question to ask,

25
00:01:36.395 --> 00:01:38.860
and the competitor feed adds market
context.

26
00:01:40.570 --> 00:01:44.290
We can also reopen the related-company
audience when planning outreach.

27
00:01:46.070 --> 00:01:48.570
The research stays close to the work it
supports.

28
00:01:50.170 --> 00:01:52.490
For recurring research, set up a Sentinel.

29
00:01:54.070 --> 00:01:55.935
Choose the audience, set a monthly
schedule

30
00:01:55.935 --> 00:01:57.800
and cap the run at one company.

31
00:02:02.170 --> 00:02:04.040
Preview the target, then approve it.

32
00:02:07.070 --> 00:02:09.970
We're running this one manually so you can
see the result.

33
00:02:12.170 --> 00:02:14.460
The run completes in twenty-three seconds.

34
00:02:15.770 --> 00:02:19.850
It researched Wychavon District Council,
and the findings are saved here.

35
00:02:22.070 --> 00:02:24.827
Open the intelligence and there's a
planned application

36
00:02:24.827 --> 00:02:26.550
for Wychavon Town to investigate.

37
00:02:29.070 --> 00:02:31.370
You can inspect the source before acting
on it.

38
00:02:35.170 --> 00:02:36.816
The work stays in your workspace,

39
00:02:36.816 --> 00:02:39.560
so the next question can use the context
you've gathered.

40
00:02:41.070 --> 00:02:43.243
Keep working here in EM3A,

41
00:02:43.243 --> 00:02:46.720
or connect a compatible AI assistant
through MCP.

42
00:02:49.070 --> 00:02:51.480
You choose what to delegate and what to
review.

43
00:02:54.270 --> 00:02:55.270
Bring us a project.

44
00:02:56.270 --> 00:02:58.530
Let's see what EM3A can do for your team.