Templates — documents, decks and offers¶
Binabik has three templates: a Word template for documents, a PowerPoint
template for decks, and a separate offer template for customer offers and
Proof of Concept proposals. All three live on the shared Google Drive under
10_Company, and all three are already styled — fonts,
colours, cover page, headings, layouts — so you write content instead of formatting
it.
Install the three brand fonts first
The templates are built on Space Grotesk, Plus Jakarta Sans and JetBrains Mono. If they are not installed on your machine, Word and PowerPoint silently substitute something else: the text re-flows, lines break in new places, and the document looks broken to whoever opens it next. There is no warning when this happens.
All three are free Google Fonts and take two minutes to install → Brand — fonts & style.
Word — documents¶
Word template on Drive Binabik_Template.dotx
The folder holds the same template twice:
Binabik_Template.dotx— the real template. Save it to your Word template folder and it appears under File → New, so every new document starts branded. On macOS that folder is~/Library/Group Containers/UBF8T346G9.Office/User Content/Templates; on Windows it is%APPDATA%\Microsoft\Templates.Binabik_Template.docx— the same thing as a normal document, if you would rather just open it and Save As.
Good to know when you write:
- Use the named styles, not manual formatting. The Styles gallery has everything you need: headings, lead paragraph, bulleted lists, captions, figure frames, callout and note boxes, references, tables. Applying a style keeps the document consistent and lets us restyle later without touching your text.
- The contents page is a Word field. Right-click it and choose Update Field to build or refresh it. Delete it if your document does not need one.
- The template ships with style-reference pages showing every element in place. Copy what you need, then delete those pages.
PowerPoint — decks¶
PowerPoint template on Drive Binabik_Deck_Template.potx
Same idea, same two flavours:
Binabik_Deck_Template.potx— the template. Drop it in the same Office template folder as the Word one and it shows up under File → New from Template.Binabik_Deck_Template.pptx— a ready-made deck with one example slide per layout, to open and Save As.
The deck is 16:9 and the brand colours and fonts are installed as the theme, so PowerPoint's colour and font pickers already offer the right ones.
Build slides from the layouts. Press New Slide and pick a layout instead of drawing your own boxes — the furniture is already positioned, you only fill in the placeholders. Eight layouts are available:
| Layout | Use it for |
|---|---|
| Cover | The opening slide: small label, title, one-line subtitle, contact block. |
| Section divider | A number and a title before each block of slides. |
| Title and content | The workhorse: a small label, a title, then text or bullets. |
| Two panels | Any contrast — in scope against out of scope, us against the alternative. |
| Three cards | Three principles or propositions, one idea per card. |
| Figure and caption | One figure, one point. |
| Statement | A single sentence the room should remember. Once per deck. |
| Closing | The last slide: closing line and contact block. |
Two habits that keep decks readable: one idea per bullet, under about twenty words and five bullets at most — more than that means the slide is doing two jobs — and leave the cover and closing dark with everything between them light, which is what makes a deck read as a document rather than a pitch.
Offers — a template of their own¶
A customer offer or Proof of Concept proposal does not start from the deck template above. It has its own 22-slide template, built on the same master so it looks like everything else we send. What makes it different is that most of it is already written.
Offer template on Drive Binabik_Offer_Template.potx
Only seven slides are yours to write¶
The other fifteen are the commercial position: how the work is staged, the three ways it can be structured, payment terms, travel rates, who brings what to the demonstration, who owns the IP, how the project runs. Each of those exists because an earlier offer went out without it. Leave them as they are. If one is wrong for a customer, that is worth a conversation and a change to the template for everyone, not a quiet edit in one deck.
| Slide | What you do |
|---|---|
| 1 Cover | Use case, customer, platform, offer number, validity date |
| 2 What we propose, in one page | Duration and the two short paragraphs. The milestone count and total follow from slide 6 |
| 3 Three stages | Nothing |
| 4 What the robot will do | Four rows: task, part, platform, outcome, plus a short lead paragraph |
| 5 Included now, and what follows | The first column. The other two are usually right as written |
| 6 Delivery plan and price | Milestone names, one line each, and a price per milestone |
| 7 Three ways to structure this | Nothing, but read it before you send |
| 8 The commercial frame | Payment days and currency |
| 9 Travel and on-site rates | The rates, once. Then it stops being per-offer work |
| 10 Bringing your team along | Nothing. Two packages on purpose, one included and one priced |
| 11 to 15 | Nothing |
| 16 to 21 Contacts | Keep the person who will run the project, delete the rest |
| 22 Closing | Nothing |
Slide 4 is four rows on purpose. The step-by-step breakdown belongs in a technical annex, not on the slide the customer reads first.
Slide 6 draws at most five milestones. If you have six, merge two. Do not shrink the type to fit.
Where the customer's questions are already answered¶
Most things a customer asks are on a slide already. Point at it instead of writing a new one:
| They ask | Slide |
|---|---|
| Is this a prototype? Does it scale? | 3 |
| Safety, CE, data protection, IT security, AI regulation? | 12, support on request |
| Payment terms? | 8, restated under the milestone table on 6 |
| What exactly is your role? | 2 |
| Is travel included? | 9, with rates so the answer is a number |
| After-sales support? | 5, available on request |
| Can you train our engineers? | 10 |
| How do we work together? | 14 |
| Who owns the software? | 13 |
| Do we get the robot, and for how long? | 11, agreed demonstration days only |
| Why a fixed price? What if we provide the robot? | 7 |
| Do you commit to a throughput target? | 3, not at this stage |
| Can we keep this confidential? | 15, we ask, you may decline |
Three rules specific to an offer¶
Never invent a price or a date. A [bracket] the customer can ask about is
better than a number that turns out wrong. Two kinds of bracket exist: a leftover
[Milestone name] means content was never written and is a defect, while
[valid until, to confirm] is deliberate and fine to send. Scan for them and know
which is which.
Currency matches the customer. CHF for Swiss entities, EUR for EU ones,
apostrophe separator, CHF 40'000. Mark indicative prices as indicative and
optional items as optional, on the slide itself.
Keep the staged tone. Nothing is phrased as a refusal: it is included in this stage, planned for the next, or available on request. The customer reads the same commercial position as a plan rather than as a list of exclusions.
Or let Claude lay it out¶
If you have the content but not the time, three Claude skills write straight into these templates — one for decks, one for documents, one for offers: Claude skills — decks & documents.
Before you send anything out¶
Open the file in Word or PowerPoint itself and page through it. Text that overflows a placeholder is invisible in an export and obvious to a customer. If you convert to PDF on a machine without the brand fonts installed, expect the line breaks to shift — export from your own machine instead.
On an offer, two more checks: the numbers on slide 2 match the table on slide 6, and the contact page you kept is the person who will actually run the project.