> For the complete documentation index, see [llms.txt](https://docs.softwaresecured.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.softwaresecured.com/planning/kickoff-call.md).

# Kickoff call

As a part of the pentest checklist, <code class="expression">space.vars.company\_name</code> requests a kickoff call between the pentesting team and the customer's pentest primary owner.&#x20;

<code class="expression">space.vars.company\_name</code>'s best practice is to schedule this kickoff call 1-2 business days before the test start date, and no later than within the first few hours of the first day of testing.&#x20;

This call gives you time to ask questions and provide information to the testing team, including:&#x20;

* the pentest checklist
* any specific requirements your team has for reporting
* project components, and
* an application or product demo.&#x20;

***

### Pentest Primary Owner

If multiple people are involved in the test, designate a primary point of contact in your organization to whom all communications will be addressed and channeled during testing. The Pentest Manager will reach out to confirm who the primary contact is.&#x20;

To keep communication optimal and the test on track, the primary contact will take ownership of the communication on behalf of your team.&#x20;

***

### Project Components

If your project contains large assets that can be split into separate logical components, we will ask you about this option in the kickoff call. These components help organize the tests findings by associating them with one or more components in the project, which can greatly simplify any separation concerns and reporting requirements that might occur after your pentest is complete.

{% hint style="info" %}
For more information on how Project Components can simplify your vulnerability management, please see [Project components](/planning/kickoff-call/project-components.md)
{% endhint %}

***

### Application Demo

During the call, we will ask for a demo of the application that includes the following information:

* Provide a general technical overview.
* Demonstrate the top 4-5 use cases; perform these demos in the specific environment that is provided for testing, if possible.
* Validate that the application and environment is fully accessible, functional, and configured before the start of the test; identify any gaps to prevent delays.
* Answer any follow-up technical questions about the overview and demo.&#x20;

{% hint style="warning" %}
Ensure that all primary technical contacts are present to address any technical questions about the target environment.
{% endhint %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.softwaresecured.com/planning/kickoff-call.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.