The exploit lands. msfconsole prints the line everyone wants to see, a Meterpreter session opens, and there's that small rush of "it worked." On a junior pentester's first few engagements, this is where the momentum quietly stops. The session gets a quick sysinfo, a screenshot for the report, and the finding gets written up as "remote code execution achieved." Box checked, move to the next host.
That's the exact point where the actual value of the assessment hasn't happened yet.
A shell answers one question. The client is paying for the next three.
Getting execution proves a vulnerability is exploitable. It does not prove what an attacker with that access could actually do to the client's environment, and "what could an attacker actually do" is the question a pentest report exists to answer. A finding that stops at "we got a shell" tells the client less than they're paying for.
What the session should actually get used for
Confirm what you're really running as. getuid and sysinfo tell you whether this is a low-privilege service account or something with real reach, and that changes the severity of the finding more than the initial exploit does.
Check whether the box is a dead end or a stepping stone. route add through the session and a portfwd rule can reach an internal-only segment that was never reachable from outside, which is often the actual headline finding: not "we got a shell," but "this one exposed host gave us a path to the internal network."
Document it in a way the client's blue team can reproduce and verify, not a transcript of ad hoc console commands typed in the moment. A .rc resource script that replays the exact sequence, and a payload built with msfvenom rather than hand-assembled each time, turns "trust me, I did this" into something the client can re-run and confirm themselves.
Why this is the actual skill gap
None of this is exotic. It's the difference between treating Metasploit as "the tool that gets me a shell" and treating it as the automation layer for everything that has to happen after the shell, in a way that produces evidence instead of a war story. That post-exploitation and automation workflow, pivoting, resource scripts, msfvenom for repeatable payloads, is exactly what Codelivly's Metasploit Post Exploitation Handbook covers. If you want the reverse-shell and payload fundamentals first, the free exploitation fundamentals path is a solid place to start before automating any of it.
