Skip to content

Tools

public

A few fundamental tools are available at Nebulab to help at work. This section is a quick recap of what tools we use and why we use them.

We don’t like to re-invent the wheel so almost all of the tools we use at Nebulab are external services. We strive to use as few tools as possible to avoid tool-fatigue.

The Essentials section on the Bob homepage links to every tool you might need.

Everyone gets a Google account in the form namesurname@nebulab.com.

That Google account is used for:

  • logging into in to the tools described in this page
  • your main work email
  • work/social events on Google Calendar
  • video calls through Google Meet
  • company files (i.e. All-hands recordings, async updates) on shared Google Drives

Being proficient in using Google Calendar is crucial to never miss a thing in your life at Nebulab. Whether it’s a client meeting, a social event or the All-Hands meeting, everything happens through a calendar event!

You can use the following template as a signature in your work emails:

--
[Your full name]
[Role], Nebulab
https://nebulab.com

Our office. Communication explains how we use it and our channel conventions.

Our HRIS software. It’s the single source of truth for team data, here’s what you can find in it:

  • team directory (with interesting people bios and skills + private data not everyone has access to)
  • attendance tracking (clock-in/clock-out and PTO)
  • documents archive (i.e. your contract)
  • company updates
  • who’s out on a holiday
  • birthdays and anniversaries
  • onboarding and flows
  • tasks
  • growth and performance: 1:1 agendas and notes, feedback, competency matrices and development plans, engagement surveys, performance reviews and compensation reviews (see Growth)

Bob stores data about yourself that could be sensitive and it’s best kept private despite being essential for working at Nebulab.

Whenever in doubt, look at the list of fields on your profile: the data category description says who the data is shared with.

Our own app for business development and delivery planning, built and run by us. It is where we plan and publish marketing content, run events, manage leads, deals, quotes and contracts, and schedule people on client engagements. Sign in with your Nebulab Google account once an Admin has added you.

Its sections follow the work:

  • Content: the content calendar, the Pipeline and Backlog of content pieces, campaigns, and the Archive of everything we’ve published. See Content planning.
  • Events: the events we run, sponsor and attend, with their planning, budgets, speakers and sponsors. See Events.
  • Sales: our CRM (people, companies, deals, lists, tasks and email), quotes, contracts, and the forms on our website. See Sales.
  • Delivery: engagements and the Schedule of who works on what. See Team allocation.

The Dashboard shows what needs you today, and Reports show how content, sales and delivery are doing. Launchpad notifies you in the app, on Slack and by email; choose which notifications you get in Settings.

Agents work in Launchpad as you: connect Claude or another AI client to its MCP server from Settings › AI clients, or create an API key for its REST API in Settings › API keys. The Launchpad for Chrome extension publishes LinkedIn posts, collects their metrics, and adds people from LinkedIn to the CRM.

Where our code and this knowledge base live.

Where the agendas of meetings with several people live, along with the action items those meetings produce. 1:1s live on Bob instead. We use Fellow for what a meeting plans and assigns, not for what is said in it: its recordings, transcripts and AI summaries go unused, because Fireflies holds the record of the call.

  • Notes follow the calendar. Fellow creates a meeting’s note from its calendar event. A recurring meeting’s note appears only when the meeting starts, so to prepare one earlier, open the event in Fellow and create the note.
  • Recurring meetings use a template. Each section has a heading and a short subtitle saying what goes in it. Add your points to the section they belong to rather than at the bottom: people read the note live during the call and follow its usual shape.
  • A talking point belongs to whoever raises it. Assign it to yourself when you add it, so everyone knows who brings it up.
  • Action items come from the agenda. Write one into the note, assigned and with a due date, and Fellow tracks it from there.

Records and transcribes our calls, and its transcript is the record of what was said. Client calls are archived to the project’s shared drive, as Project management describes.