• Job Type: 2-3 week engagement
• Location: Remote
• Salary: Day rate negotiable
• Responsibilities: Delivery of services and recommendations

1) The company

Bora is a cybersecurity marketing agency. We only work with cybersecurity companies. We only do marketing.

Our team includes writers, strategists, account directors, and project managers. Most of us are already using AI in some form, but inconsistently and without a shared framework. This engagement is about changing that.

2) What we’re trying to do

We have a clear picture of our client engagement workflow — 12 stages from brief to reporting — and we have started mapping where AI fits alongside it: which tasks are good candidates for automation, which need human judgement, and where a well-designed skill could save time.

We need someone to help us turn that thinking into a working system. We are not looking for a developer to execute a fixed spec. We’re looking for a consultant who can work with us to figure out the right setup, challenge our assumptions, and then help us build it.

In broad terms, the outcome we want is:

• Claude configured and structured as our primary AI interface, with the right context, permissions, and project setup for our team to use it confidently and consistently
• Google Workspace (Docs, Drive, Gmail) integrated into our AI workflow in a way that makes sense for how we work — open to advice on what that looks like
• Key tools connected: Asana (project & ticket management), Fathom (meeting recordings and transcripts), Canva (design), and WordPress (content publishing)
• A library of ~25 Claude micro-skills that automate specific subtasks in our workflow — each one narrow in scope, human-supervised, and triggered by a command

We have a clear view of the skills we want to build, but we are open to being challenged on the approach. If there is a better way to structure this — different tooling, a different architecture, a phased approach we haven’t considered — we want to hear it.

3) The engagement

2-3 weeks, embedded in our team for that period. Available during working hours, attending relevant internal meetings, and working closely with our account directors who will be the primary users of what gets built.

Phase 1: Discovery and setup

Understand how we work, review our workflow in detail, audit our current tool setup, and give recommendations — a short, written output at the end of this phase before any building.

Phase 2: Build

Build the skills and integrations based on the agreed plan. Account directors and project managers should be involved in testing from day one.

Phase 3: Refine, document, and hand over

Iterate based on feedback and use, complete documentation, and make sure the team can operate the system independently. The engagement ends with a handover session and a written guide that a non-technical team member can follow.

We’re flexible on exact timing and structure. If you have a different approach in mind, tell us.

4) What good looks like

In broad terms, the outcome we want is:

• A Claude setup our team can use from day one, with the right project structure, context, and guardrails in place
• A library of working micro-skills — documented, tested, and handed over with clear instructions
• Google Workspace integrated in a way that reduces friction, not adds to it
• Our key tools (Asana, Fathom, Canva, WordPress) connected and working within the workflow where it makes sense
• Recommendations for other integrations that may serve us well