Answering your question with a question is not only Jewish, but also Israeli. How do you prefer to work? · If you have elected to work hourly, then we can edit from here to next month, as many times as you want, since we’re clocking, reporting and billing our time. · If, however, you have chosen the price per deliverable or project model, then all deliverables come with one original draft and two rounds of edits. · Ideally, 80% of the edits will be identified, communicated and resolved in the first round - this is the content round and should resolve the following: What information is missing? Does the logic flow? Are the subheadings appropriate and accurate? Is the angle/story correct? Is the voice and tone on brand? Are there any inaccuracies in claims that we’re making or in data that we’re using? The second round of edits (final 20% of editing) should be tiny tweaks: Corporate branding/messaging inconsistencies Preferred phrasing, wording, tense or singular vs. plural

We like money. · We’re happy to accept your funds in any currency at any time (not cryptocurrency, though - the Israeli government frowns upon it) as long as we can figure out - legally and cost effectively - how to invoice you and transfer payment from wherever you are - to Israel. · We’ve worked with clients in the USA, UAE, and all across Europe, although heads-up: international wire transfers (including Paypal and its competitors) require a fee or percentage, which we share 50/50 with our international clients.

That’s like asking how long it takes to make a dress. What does the dress look like, and how many other dresses is the designer creating simultaneously? Is the fabric already ordered? Is there a pattern? Have three other designers failed at creating this dress? Why? · Usually, once we have learned a client, turning a brief into a blog (first draft) takes three business days. · Onboarding a new client, however, can take up to two weeks, since we need to review current collateral, ask our questions, and get on a launch call to walk through product, market, audience, pain points and tone. · We often have a waiting list, especially surrounding Pesach (April), August, and Chagim (October). We are careful about the number of clients we take and how often we take new projects because we like to make deadlines, but we also prefer to remain calm, organized, and methodical. Plus, we like our weekends.

That would be a resounding no. · While we often attend discovery and launch meetings in Hebrew, and can work with raw materials in Hebrew, we do not produce Hebrew language content. · Keep in mind, when looking for Hebrew content, that when you’re aiming at an Israeli audience, you cannot simply translate your content from English to Hebrew. Israelis expect to be “pitched” more directly than American or European audiences, and they want you to get to the point quickly. Rather than translation from English to Hebrew, you’ll need transcreation to account for the cultural difference.

The vast majority of our clients are B2B. · At least 75% of our portfolio is tech-based B2B. Some are SaaS, some are cybersecurity, and we work with IoT, augmented reality, and artificial intelligence. We do, however, have a smattering of B2C clients and a few in the nonprofit arena. Tachliss, (a Hebrew term that mostly means “bottom line” but the concept is so much stronger in Hebrew that it’s a better language for this point) we work predominantly in tech because: There is almost always one point of contact. There is usually some existing collateral, at some level, to work from. Decisions are swift and final. There is a ton of work available. Tech companies almost always have an established, seamless vendor onboarding and payment process. It’s not that we were born to live and breathe tech, but the content is fascinating and learnable, and the process is consistently efficient. We also enjoy food and shelter, so a steady, reliable source of content and process (and therefore income) is key when we are selecting clients.

Reluctantly, yes. · Reluctantly not because we don’t want to offer discounts (our nonprofits are indeed charged less than our corporate clients) but because we’re hesitant about nonprofits altogether. While we respect our nonprofit clients tremendously, we have learned that the decision-making process and bureaucracy to be expected at nonprofits can be challenging. · If you represent or run a nonprofit, we’d be happy to speak, but please do understand that we’re… reluctant.

Forgive us, but tech writing is boring. · Our exposure to tech writing is predominantly manuals and instructions for an audience of developers or other technically-adept users. The point is to translate tech-speak into methodical yet consumable tech instructions. · What we do is marketing writing. · Yes, we can translate complicated or convoluted concepts with many moving parts into consumable, informative, enlightening (and even potentially entertaining) marketing content, even using jargon familiar to the target audience. That takes time, but we are almost universally enthusiastic about climbing that learning curve. · But we don’t write instructions, wiki entries, or manuals (that’s a tech writer) and we avoid writing for an extremely tech-savvy audience (developers, system administrators, open-source enthusiasts, purely on the tech side rather than the business side) since often that means our learning curve is too steep.

Not if I can help it. · My husband and I have both worked from home for the past decade; I consider us pre-COVID trailblazers. Finally, the world has caught up with us and everybody works at least on a hybrid model. · I’m based on a small moshav in the Jerusalem Hills, I can see my (14) ducks from my office, and I conduct my entire business via phone/email/Zoom/WhatsApp/Trello, and always have. I almost never ask my team to leave their homes or shed their jammies. On rare occasions, I visit client sites personally, but only when they promise a test drive of their augmented reality glasses (looking at you, Lumus.)

Answering your question with a question is not only Jewish, but also Israeli. How do you prefer to work? · If you have elected to work hourly, then we can edit from here to next month, as many times as you want, since we’re clocking, reporting and billing our time. · If, however, you have chosen the price per deliverable or project model, then all deliverables come with one original draft and two rounds of edits. · Ideally, 80% of the edits will be identified, communicated and resolved in the first round - this is the content round and should resolve the following: What information is missing? Does the logic flow? Are the subheadings appropriate and accurate? Is the angle/story correct? Is the voice and tone on brand? Are there any inaccuracies in claims that we’re making or in data that we’re using? The second round of edits (final 20% of editing) should be tiny tweaks: Corporate branding/messaging inconsistencies Preferred phrasing, wording, tense or singular vs. plural

We like money. · We’re happy to accept your funds in any currency at any time (not cryptocurrency, though - the Israeli government frowns upon it) as long as we can figure out - legally and cost effectively - how to invoice you and transfer payment from wherever you are - to Israel. · We’ve worked with clients in the USA, UAE, and all across Europe, although heads-up: international wire transfers (including Paypal and its competitors) require a fee or percentage, which we share 50/50 with our international clients.

That’s like asking how long it takes to make a dress. What does the dress look like, and how many other dresses is the designer creating simultaneously? Is the fabric already ordered? Is there a pattern? Have three other designers failed at creating this dress? Why? · Usually, once we have learned a client, turning a brief into a blog (first draft) takes three business days. · Onboarding a new client, however, can take up to two weeks, since we need to review current collateral, ask our questions, and get on a launch call to walk through product, market, audience, pain points and tone. · We often have a waiting list, especially surrounding Pesach (April), August, and Chagim (October). We are careful about the number of clients we take and how often we take new projects because we like to make deadlines, but we also prefer to remain calm, organized, and methodical. Plus, we like our weekends.

That would be a resounding no. · While we often attend discovery and launch meetings in Hebrew, and can work with raw materials in Hebrew, we do not produce Hebrew language content. · Keep in mind, when looking for Hebrew content, that when you’re aiming at an Israeli audience, you cannot simply translate your content from English to Hebrew. Israelis expect to be “pitched” more directly than American or European audiences, and they want you to get to the point quickly. Rather than translation from English to Hebrew, you’ll need transcreation to account for the cultural difference.

The vast majority of our clients are B2B. · At least 75% of our portfolio is tech-based B2B. Some are SaaS, some are cybersecurity, and we work with IoT, augmented reality, and artificial intelligence. We do, however, have a smattering of B2C clients and a few in the nonprofit arena. Tachliss, (a Hebrew term that mostly means “bottom line” but the concept is so much stronger in Hebrew that it’s a better language for this point) we work predominantly in tech because: There is almost always one point of contact. There is usually some existing collateral, at some level, to work from. Decisions are swift and final. There is a ton of work available. Tech companies almost always have an established, seamless vendor onboarding and payment process. It’s not that we were born to live and breathe tech, but the content is fascinating and learnable, and the process is consistently efficient. We also enjoy food and shelter, so a steady, reliable source of content and process (and therefore income) is key when we are selecting clients.

Reluctantly, yes. · Reluctantly not because we don’t want to offer discounts (our nonprofits are indeed charged less than our corporate clients) but because we’re hesitant about nonprofits altogether. While we respect our nonprofit clients tremendously, we have learned that the decision-making process and bureaucracy to be expected at nonprofits can be challenging. · If you represent or run a nonprofit, we’d be happy to speak, but please do understand that we’re… reluctant.

Forgive us, but tech writing is boring. · Our exposure to tech writing is predominantly manuals and instructions for an audience of developers or other technically-adept users. The point is to translate tech-speak into methodical yet consumable tech instructions. · What we do is marketing writing. · Yes, we can translate complicated or convoluted concepts with many moving parts into consumable, informative, enlightening (and even potentially entertaining) marketing content, even using jargon familiar to the target audience. That takes time, but we are almost universally enthusiastic about climbing that learning curve. · But we don’t write instructions, wiki entries, or manuals (that’s a tech writer) and we avoid writing for an extremely tech-savvy audience (developers, system administrators, open-source enthusiasts, purely on the tech side rather than the business side) since often that means our learning curve is too steep.

Not if I can help it. · My husband and I have both worked from home for the past decade; I consider us pre-COVID trailblazers. Finally, the world has caught up with us and everybody works at least on a hybrid model. · I’m based on a small moshav in the Jerusalem Hills, I can see my (14) ducks from my office, and I conduct my entire business via phone/email/Zoom/WhatsApp/Trello, and always have. I almost never ask my team to leave their homes or shed their jammies. On rare occasions, I visit client sites personally, but only when they promise a test drive of their augmented reality glasses (looking at you, Lumus.)