Read the examples
JavaScript is off. Audio still works above; the full text and sources are also available here.
Alex’s complete briefing
Hi, Alex! Let’s start with a typeface request that grew into something much bigger. A museum asked for a serif for its members’ magazine and ended up with four type families and eighty pictograms. The interesting part is how A2-Type got from that first request to something the Louisiana Museum of Modern Art could use across the whole museum.
It’s Nice That covered the project in October. A2-Type explored the Danish museum’s printed archive and found a history of sans serifs, less frequent serifs, and condensed poster lettering. Those three categories helped shape the new system.
So the archive did more than supply attractive old letters. It helped determine which kinds of typefaces to make. There was already a range of voices in the museum’s history; the designers had something specific to work from.
Then they took the fonts back into the museum and tested them with the team, at different sizes and on different surfaces.
The building gave them another source to work with. Louisiana began as a private villa, then grew into a complex of Danish modernist buildings. The designers describe pavilions and corridors, changes of level, and contrasts between glass, steel, wood, and the surrounding landscape. That variety fed into the differences between the typefaces. So the system wasn’t only looking backward through old posters. It was responding to the place visitors move through today.
The four families are Louisiana Grotesk, Mono, Antikva, and Plakat. The commission also extended into those eighty pictograms for use inside and outside the museum. Letters and wayfinding symbols were being developed as related parts of the same environment, rather than two unrelated visual projects.
I like that approach to consistency. The typefaces share a starting point, but one face doesn’t have to do every job. For an identity you’re taking from packaging to a website, that’s an interesting possibility: keeping a family resemblance while giving each format a little room.
When you look at the images, try the Lucian Freud exhibition posters, then the magazine cover. Compare the space given to the name, the image, and the supporting text. What still feels recognizable as the format changes?
Now, from the lettering on a package to something less visible: what its barcode needs to do.
GS1 US calls its initiative Sunrise 2027. The goal is to get retail checkouts ready to scan and process two-dimensional barcodes, including QR codes built to GS1 standards.
A QR code that opens a brand’s website isn’t enough to identify a product at checkout. It needs the appropriate standardized product identifier, and the retailer’s systems have to be able to process it.
With those pieces in place, the same code can identify the item at checkout and let a shopper access product information on their phone. Additional data, such as expiration dates, can support other uses as brands and retailers develop their systems.
But 2027 isn’t a universal deadline to remove UPC barcodes, or to have every possible feature working. GS1 describes a gradual approach: crawl, walk, run.
Your coffee client is still working out the product format and considering cartons. If it’s going into stores, there’s a question worth settling before the layout is fixed: what will those retailers expect the codes to do?
That could affect how much space the design needs. It doesn’t mean recommending a new barcode before there’s a reason to use one.
Let’s stay with packaging for a moment. When a supplier shows you a promising material, what, exactly, was tested? A flat sheet, an assembled package, or the package with the actual product inside?
Packaging scientist Claire Koelsch Sand explains why that matters in a 2024 Food Technology article. Creasing, cutting, printing, and storage conditions can create tiny cracks or pinholes in a paperboard coating. A barrier that keeps moisture or grease from passing through a flat sheet may lose some protection during production.
For some food-contact applications, she describes applying the coating after the container has been formed. That can avoid damage from forming and help seal the joins. So the order of production matters too, not just the sample you’re holding.
For your carton project, that depends on what the carton will do. Protecting the food directly is different from being an outer box around another package. There’s no need to choose a coating yet.
Sand brings it down to a very concrete example: testing a hot-chocolate cup with hot chocolate, for the time someone will actually use it. That’s a different promise from a flat sheet passing a test. You want to know which one the supplier’s results describe.
She also separates properties that can get bundled together under the word “barrier.” A coating may need to resist water vapor or oxygen, hold its shape when wet, and keep a seam intact. Those aren’t interchangeable tests. Her examples show why the contents, the joins, and the intended time of use belong in the same conversation as the paperboard itself.
And finally, a different kind of looking: what do children photograph when they get to choose? Annebella Pollen went searching for their pictures in places including secondhand markets and house clearances. Museums, she explains, haven’t tended to value them. Her book, Whippersnappers, came out in September and was covered by It’s Nice That in October.
Her search started with children’s photographs from around the turn of the twentieth century, after Kodak marketed the Box Brownie to children. Museum and school collections often led nowhere. Asking older photographers for their first pictures opened another route: childhood images that had never been published, with the stories of the people who made them. The history was sitting in private collections as well as institutions.
In a Kodak research project in 1999, children were given disposable cameras to use freely. Pollen describes them finding adult photography too proper. Their own pictures included friends making rude gestures and dogs wearing sunglasses and hats.
There’s something lovely about letting those choices stand. The ordinary family photograph makes room for what the children themselves thought deserved a picture.
Sources
A2-Type and Louisiana Museum of Modern Art
itsnicethat.com
Sunrise 2027 and 2D barcodes
gs1us.org
Paperboard coatings and carton production
ift.org
Whippersnappers: How Children Became Photographers
itsnicethat.com
Whippersnappers: How Children Became Photographers
fourcornersbooks.co.uk
Simulated setup
BEKABLE: Tell me a little about yourself: your first name, age, and what you do for work.
Alex: Alex, 34. Freelance graphic designer in Portland.
BEKABLE: What kind of projects do clients usually hire you for?
Alex: Branding and packaging. Mostly small food and drink brands. Sometimes their websites and product images too.
BEKABLE: What would you like to keep up with? It can be about your work or just something you’re interested in.
Alex: Design, mostly. Branding, type, packaging. What smaller studios are making. Useful tools and AI too, but I don’t want a feed full of product launches. I’d like to find good ideas and keep up without reading six newsletters every morning.
BEKABLE: What kinds of visual work make you stop and take a closer look?
Alex: Typography, interesting colors, clever packaging. Small studios doing good work with small budgets. Not the same brands everyone keeps posting.
BEKABLE: What else do you find yourself reading or looking at, even when it has nothing to do with a client project?
Alex: Independent magazines, photography, old signs and lettering. I like seeing how people make things. I don’t always need to turn it into an idea for a client.
BEKABLE: With photography, are you more interested in the work and the people behind it, or cameras and technique?
Alex: The work. Photo books, projects, interviews. Not camera reviews.
BEKABLE: And on the work side, what did you have to look up, check, or ask someone about on a recent project?
Alex: A font license. And I had some questions for the printer about the packaging.
BEKABLE: What were you trying to figure out with the printer?
Alex: Which finish would work. The client wanted something that looked premium but didn’t cost too much. I could tell them what I liked, but I wasn’t great at explaining the tradeoffs.
BEKABLE: Would you like to be more involved in those decisions, or mainly get clearer specifications before you start designing?
Alex: More involved. I’d like to get brought in before everything’s decided, instead of just making the label fit.
BEKABLE: What would help you make a stronger recommendation at that stage?
Alex: Knowing what’s possible at their budget. Examples I could show them. Being able to explain why one option is worth paying for.
BEKABLE: When a project includes details about materials, printing, or budget, I’ll bring those in too. They could help with those conversations.
Where do your clients sell their products?
Alex: Mostly online and in independent stores in the US. A couple are trying to get into regional grocery chains.
BEKABLE: When they move into those stores, what changes in the work they ask you to do?
Alex: Different pack sizes, sometimes display boxes. And the product needs to make sense on a shelf, not just in a nice photo.
BEKABLE: That gives me a reason to watch shelf presentation and retail packaging requirements alongside design references. Are you responsible for the information on the label too?
Alex: The client supplies the wording and nutrition information. I lay it out. I’d still like to know if something might affect the space or the design, but I’m not their compliance person.
BEKABLE: What tools do you use for the work you’d most like to speed up?
Alex: Illustrator and Photoshop, mostly. Figma for websites. Mockups and adapting visuals take time. I’m interested in AI for exploring ideas, but not for handing a client a generated final logo.
BEKABLE: You mentioned checking a font license. Which other rights questions come up in your work?
Alex: Stock photos, mockup assets, sometimes illustrations. Clients send things they found online too. With AI, I’m unsure what I can use commercially and what happens to files I upload.
BEKABLE: Is there a project or change coming up that deserves extra attention for a while?
Alex: A coffee client is considering cartons for a new product. They’ll choose suppliers in the next couple of months. Sustainability will come up, but I want practical information, not marketing claims.
BEKABLE: Do you already know what the carton will need to hold or protect?
Alex: Not yet. They’re still figuring out the product format.
BEKABLE: I’ll keep that exploratory for now: useful material and print options, with their limitations, rather than recommendations for a package we haven’t specified.
Outside client projects, is there anything about running your business you’d like to understand better?
Alex: Pricing bigger branding projects. I’m trying to move away from lots of little one-off jobs. But I don’t want a daily dose of freelance hustle advice.
BEKABLE: Concrete examples of project scope and pricing could be useful occasionally, then. I’ll keep them behind the design and production topics.
How would you like the briefing to sound?
- Casual and direct
- Friendly and relaxed
- Professional and approachable
- Formal and concise
Alex: Friendly and relaxed. No long intro, and don’t explain basic design terms.
BEKABLE: How much time would you usually want to spend listening? (Six minutes, twelve, or any length you prefer.)
Alex: About six minutes. I’ll open the images and sources afterward if something interests me.
BEKABLE: I’ll keep you up to date on branding, type, packaging, and what smaller studios are making. There’ll also be room for the things you follow out of curiosity: independent magazines, photo books and projects, lettering, and how things are made. For photography, I’ll focus on the work and the people, not gear reviews.
I’ll watch developments that could affect your client work too: printing and materials, packaging for retail, and labeling changes that could affect a layout. When a project explains its production choices, those details may help you talk through options with a client. Other pieces can simply be worth seeing or reading.
For tools, I’ll focus on your Adobe and Figma workflow, mockups, adaptations, and early exploration with AI. Rights coverage will include fonts, stock assets, client-supplied material, and AI terms, not just AI copyright news.
The carton project will get extra attention while the options are open. Sustainability coverage will focus on materials, processes, and evidence. Occasionally, I’ll include a useful example of how a larger branding project was scoped or priced.
I’ll start with US-relevant practical information and look more widely for creative references. If that scope misses part of your work, you can change it.
About six minutes, straight into the substance, with images and original sources in the written version. What would you change?
Alex: Keep design and inspiration first. The business stuff is useful, but only when there’s something really specific.
BEKABLE: Got it. Design and inspiration come first; business topics only earn a place when there’s something concrete you can use.
On quieter news days, I can bring in a closer look at a process, a project, or a question you’re interested in. I’ll make it clear when something is an older reference rather than new news.
I have what I need to create your personalized daily briefing.
Below each briefing, you’ll find an “Adjust my briefing” button. Tell me what you liked, what wasn’t useful, or which topics you’d like to add or drop. You can change the tone, length, or focus there too.
You don’t need to get everything right today. Start with your first briefing, and we can fine-tune it whenever you need.
Priorities
- Branding, typography and small-studio work
- Independent magazines, photography and lettering
- Printing, materials and retail packaging
- Adobe and Figma workflows; rights and licensing
- Temporary focus: a coffee client’s carton project
Illustrative feedback
Alex: The print examples were useful. The AI section was a bit much. I’d rather get one tool I could actually use than three launches.
BEKABLE: I’ll be more selective with AI tools: fewer launches, more practical uses for your mockup and exploration work. I’ll keep important licensing or client-file changes in scope.
The print examples stay. Was there anything missing from them?
Alex: Rough costs or minimum quantities, when those are available.
BEKABLE: I’ll look for those details and include them when they’re documented. When they aren’t, I’ll say so.
I’m keeping AI as a topic, but raising the bar for tool news.
Maya’s complete briefing
Hi, Maya! Let’s start with something Gallup found about team sizes. The average is going up, but the typical team is still much smaller than that headline might suggest. Here’s what’s happening.
Gallup reported in January that the mean number of direct reports rose from 10.9 in 2024 to 12.1 in 2025. The median stayed around five or six. A minority of very large teams is pulling up the average. Twelve direct reports hasn’t suddenly become the norm.
Two-thirds of managers had fewer than ten reports. The increase came largely from a small rise in the share managing twenty-five or more people. So that headline about expanding teams needs a closer look: the change is concentrated in one part of the workforce.
There’s another part of this story: the manager’s own workload. Gallup surveyed more than sixteen thousand U.S. managers and leaders between 2022 and 2024. Ninety-seven percent reported individual contributor responsibilities. The median time spent on that work was forty percent.
Among managers spending more than forty percent on individual work, engagement was lower, and fell further as their teams grew. That’s an association with managers’ own engagement, not a measured effect on employee departures. And forty percent is the survey’s midpoint, not a recommended ceiling. For the hiring review, what’s useful is how team size and individual workload interact. There isn’t one magic number of reports hiding in these results.
Gallup also looked at feedback in a separate analysis of employees. Across seven studies, about seven in ten were highly engaged when they strongly agreed they’d received meaningful feedback in the past week. Among those who didn’t strongly agree, it was about one in four. That pattern held across team sizes. It doesn’t establish cause and effect, but it adds a useful counterweight to the headcount discussion: larger teams weren’t uniformly associated with a poor employee experience. What employees reported about their contact with the manager mattered too.
And while team sizes are changing, so are the jobs inside them. BambooHR published a finding in September that caught my attention: seventy percent of HR respondents said they included AI requirements in every newly created role, whether or not matching internal job descriptions had been updated.
So the hiring requirements weren’t necessarily waiting for an internal rewrite. AI expectations could arrive through recruitment while existing employees’ paperwork followed a different timetable. The survey doesn’t say seventy percent had conflicting descriptions; that’s a different claim.
The other answers help explain the picture. HR respondents estimated that sixty-one percent of roles needed updated descriptions to reflect AI’s impact. Seventy-seven percent planned updates within the following twelve months. Meanwhile, twenty-one percent of employees said they’d already requested an updated description and hadn’t received one.
HR respondents also said they’d updated descriptions for an average of forty-three percent of their workforce. That isn’t a figure to subtract from sixty-one and call a measured backlog; the questions describe different things. More interestingly, the reasons given for delays included moving targets, competing priorities, and anxiety about compensation. So the report describes more than slow paperwork. Expectations about the work are changing while employers are still deciding how to describe and recognize it.
That’s the figure I’d keep beside the hiring statistic. These employees were asking for an update themselves. We don’t know whether they wanted a different title, different pay, or simply clearer expectations. But the request was already there; it wasn’t just HR deciding a document needed attention.
This was a vendor-sponsored online survey of U.S. salaried desk workers, including five hundred and twenty HR managers and leaders. It gives us an outside signal about changing roles. It doesn’t tell us what’s happening inside your company.
Now, there’s a question behind all those changing AI expectations: how much more work are the tools actually helping people do? METR’s May survey offers an interesting way into that.
Technical workers reported a median threefold increase in speed with AI. But estimates of the value they produced were smaller. Across three differently worded questions, the medians ranged from 1.4 to two times. Even in the same survey, the size of the gain depended substantially on what people were asked to estimate.
METR surveyed three hundred and forty-nine technical workers, including eighty-seven software engineers. They were self-selected, and these were estimates, not productivity gains measured experimentally. The researchers warn that people can overestimate the benefit.
The value questions weren’t just asking whether people felt productive. One asked how long equally valuable work would have taken without AI. Another asked how many otherwise identical people, without AI, a team would need to replace the respondent. Those questions make people think about the contribution delivered, rather than the speed of each task. The answers still depend on judgment, and METR found differences between the measures. But the wording gives you a much clearer picture of what a productivity number actually means.
Their hypothetical dashboard example makes the distinction concrete. Imagine a researcher who could use an interactive display of their data. Building it by hand would take too long to justify. With AI, it becomes quick enough to be worth doing.
Now there’s a dashboard, and it may be useful. But that long manual build was never going to happen. Counting all those hypothetical hours as time saved would exaggerate the change in the researcher’s actual week. Those hours weren’t in the old schedule to begin with.
And once dashboards are cheap to make, you might make more of them. The work itself changes. METR calls this task substitution: a speed estimate can reflect tasks AI made newly attractive, rather than the tasks that previously filled the schedule.
There’s room here for genuine gains, including useful work that wasn’t possible before. But faster existing tasks, newly worthwhile tasks, and hours actually freed are different outcomes. A coding speedup doesn’t translate directly into spare engineering capacity. That’s the distinction I’d carry into the review, rather than using these survey multipliers as a staffing forecast.
Now, a little architecture. There’s an old coffee factory in Houston that’s becoming a music and arts school, and the way they’re bringing daylight into it is worth a look.
Construction has started at the nineteen-thirties Folger plant on Buffalo Bayou. It will become FLAMA, a tuition-free public charter school for children from pre-kindergarten through eighth grade. Opening is planned for August 2027.
OMA’s Jason Long leads the design, with RDLR Architects and landscape architects SWA. In ArchDaily’s October report, you can see how the daylight problem shapes the whole plan.
Classrooms line the perimeter, beside the factory’s existing divided windows. Those windows will be restored and adapted to school energy standards. Farther inside, circular skylights bring daylight into shared spaces. So as you move away from the windows, you move from classrooms into places for children to gather and work together.
Each floor has two central gathering areas, surrounded by classrooms in Montessori-inspired neighborhoods. Then there’s a bigger shared room: a double-height cafeteria and auditorium for lunches, assemblies, and performances, with a circular opening and a curved stair.
The shared spaces change with the children’s ages. The youngest have ground-level room for movement, play, and drum circles. Grades three through five share an open library with flexible furniture for group study, projects, and after-school activities. Above them, grades six through eight have another library with more focused study areas.
The entrance is through a private courtyard. Outside, the industrial facade remains part of the school’s identity; inside, the deep floor plan is reorganized around light and gathering. The site sits opposite Turkey Bend, a separate project reworking former industrial waterfront into public spaces and flood-adapted landscapes. There’s a larger change happening along the bayou, although neither the renderings nor the school plan tell us what the completed neighborhood will feel like.
We’re still looking at plans and renderings, rather than a finished school. But there’s one detail worth holding onto. Between the two libraries, the design includes an opening shaped like the f-hole of a string instrument: that long, curved shape in the body of a violin, enlarged into the floor.
Sources
Team size and the manager's other job
gallup.com
Job descriptions catching up with changing work
bamboohr.com
Job descriptions catching up with changing work
bamboohr.com
Faster tasks and more valuable work
metr.org
Faster tasks and more valuable work
metr.org
A coffee factory becomes a music and arts school
archdaily.com
Simulated setup
BEKABLE: Tell me a little about yourself: your first name, age, and what you do for work.
Maya: I'm Maya, 42. I lead HR at a software company in California. We're 48 people, so my day can go from a hiring discussion with the CEO to sorting out someone's leave paperwork.
BEKABLE: What would you like to keep up with, for work or just for yourself?
Maya: How work is changing. Hiring, pay, what engineers want from an employer. AI is part of that, but I don't need every new HR product. Outside work, architecture and cities. I can lose an evening reading about what happens to an old building.
BEKABLE: What catches your attention in those stories: the design itself, how a place gets reused, or what changes for the people around it?
Maya: The reuse, mostly. An office becoming housing, an old industrial building finding another purpose. But I want to see the design too. Not just read about zoning disputes.
BEKABLE: And on the work side, what are you paying closest attention to right now?
Maya: Keeping the engineers we have. We don't have the budget to match every salary out there. I'd like to understand what's really changing in the market, beyond the stories that get all the attention.
BEKABLE: Have you already seen signs in the team, or are you mostly trying to get ahead of it?
Maya: Mostly trying to get ahead of it. Nothing in particular has raised a flag for me right now. I'd rather understand what's changing before I have to react in a hurry.
BEKABLE: When you say the market, which employers are you really competing with for people?
Maya: Other smaller software companies, but remote roles at bigger companies come up too. A national headline about tech salaries usually doesn't tell me much about our situation.
BEKABLE: Where do your employees work? That will help me separate relevant pay comparisons and employment updates from things that don't apply.
Maya: Everyone's in California right now. Some work near the office, some remotely. We're not planning to hire in another state at the moment.
BEKABLE: Is there a decision coming up where that would be especially useful?
Maya: We're reviewing next quarter's hiring requests. The CEO wants to know whether every request really needs another person. I want to understand the work before we decide that a new tool means we can skip a hire.
BEKABLE: Where is AI already showing up in those discussions?
Maya: Engineering is using coding tools, and support is trying an assistant. I hear that people are saving time, but I don't know what happens to the rest of their day. I'm more interested in that than in buying an AI recruiting platform.
BEKABLE: For employment-law updates, what do you handle yourself and what goes to someone else?
Maya: I handle policies and the day-to-day questions. Payroll is with a provider. I mostly need to catch changes early enough to check whether they affect us. For the complicated stuff, I call our outside counsel.
BEKABLE: What would you happily leave out of your feed?
Maya: Generic leadership advice. Big-company benefits we could never offer. I'd still want to hear about a big company if what it's doing could affect the people we hire.
BEKABLE: How would you like the briefing to sound?
- Casual and direct
- Friendly and relaxed
- Professional and approachable
- Formal and concise
Maya: Professional and approachable, but warm. Get to the point. I know the HR vocabulary; explain the unfamiliar technical stuff when it matters.
BEKABLE: How much time would you usually want to spend listening? Six minutes, twelve, or any length you prefer.
Maya: Eight minutes. Something I can listen to before the day starts. I'll open a source later if I need it.
BEKABLE: I'll follow hiring, pay, retention, and how jobs are changing, with your 48-person software company in mind. The aim is to help you see changes coming, rather than turn every story into a warning about your team. We can narrow salary comparisons to specific roles and experience levels when you need them; for now, I'll keep those market signals broader.
Your next-quarter hiring review gives me a reason to watch changes in tasks, skills, and team responsibilities. AI in engineering and support is part of that, alongside management, workload, and how people develop in their jobs.
I'll also watch employment updates relevant to your California workforce, distinguishing adopted changes from proposals and checking which employers they cover. Those can help you prepare a conversation with your provider or counsel.
Architecture and cities will stay part of your selection too, especially buildings finding a new use, with the design and the people involved. Those stories don't need an HR lesson attached.
Eight minutes, direct and warm, with the original sources alongside the text. What would you change?
Maya: Keep the architecture. It's easy for everything I read to become work. And don't make every edition about retention just because that's what I'm dealing with this week.
BEKABLE: Understood. Retention is a current priority, not the whole briefing. Under each briefing, Adjust my briefing lets you tell me what you liked, add or remove topics, or change the tone and length. You can use it whenever something needs adjusting.
Priorities
- Hiring, pay and retention at a small software company
- California employment developments relevant to her work
- Changing roles and practical uses of AI
- Architecture, buildings and the evolution of cities
Illustrative feedback
Maya: The study about coding tools was interesting. For the hiring review, though, I need more on how support teams are reorganizing their work. That's the part I need to get my head around now. And keep the building stories. I sent one to a friend.
BEKABLE: I'll give support more attention while you're preparing the review, especially changes in tasks and who takes responsibility for them. I'll keep the broader coverage of work, and the architecture stories.
One related area worth watching is how support roles are being described in job postings. That could reveal skills employers are starting to ask for. It wouldn't prove those teams are more productive, but it could give you something concrete to compare with your own hiring requests.
Maya: Yes, that would help me go into the discussion with something concrete.
BEKABLE: When the hiring review is over, we can lower that priority without losing the broader coverage of how work is changing.
David’s complete briefing
Hi, David! Let’s start with what packaging equipment buyers are asking for. They want machines that can switch between more products and package sizes. PMMI, the packaging machinery trade association, described that shift in September. It gives a more specific picture of demand than a broad manufacturing forecast.
Across packaging, PMMI points to more single-serve and grab-and-go formats, more product varieties, and shorter runs. Buyers want that flexibility without losing too much production time whenever they switch.
The changes reach the end of the line, too. Case erecting, packing, and sealing are being combined into integrated systems. Robotic palletizing is gaining ground where case sizes and pallet arrangements change frequently. That brings both sides of your customer base into the picture: packaging machinery and material handling increasingly meet in the same equipment project.
The need may be clear, but the timing isn’t. PMMI also describes tighter discipline around capital spending. A buyer can have a good reason to replace equipment and still take longer to commit.
Materials are part of that equipment discussion, too. PMMI reports interest in modular systems that can be upgraded as packaging formats and material requirements change. A machine isn’t only being judged on the package it can run today. Buyers are also looking at what they could adapt later, rather than starting again with another dedicated line. That’s a reported direction of demand, not a forecast for any one of your customers.
The report also gives more specific examples of AI use than simply “smart factories.” It mentions capturing knowledge from retiring employees, drawing on previous projects to develop specifications, and helping troubleshoot problems. These are early applications identified in the study. They’re useful clues about where equipment builders see knowledge and workforce constraints, rather than proof of a particular productivity gain.
A separate PMMI report, released in late October, gets closer to what happens inside those projects. It draws on discussions with equipment builders and buyers at PACK EXPO. In feedback collected before the session, requirements and specifications were the most frequently identified source of buyer-seller friction.
Participants also highlighted getting plant operations and IT involved before requirements are finalized, and establishing who can approve changes. That’s feedback from the people in the room, not a measurement of delays across the whole industry.
The public summary gets quite specific about the earlier stages: preliminary requests for information, one-page concept screening, shared success criteria, and even an agreed glossary. Mid-project changes bring another question: who assesses the impact, and how quickly must they respond? I find the glossary detail revealing. The discussion wasn’t only about improving the machine. It was also about getting buyer and builder to mean the same thing before detailed engineering began. Those are themes from this session, not evidence that every delayed project has that problem.
Suppose an equipment builder says its customer still wants the line but hasn’t settled which package formats it must handle. Now compare that with a project whose funding is uncertain. Either could postpone a parts order. But one has an expressed need and open specifications; the other has an unresolved financing problem. From the outside, the wait might look the same. The conversations behind it would be quite different.
Investment announcements and disclosed orders give you market signals. Customer conversations tell you where a particular project stands. Read together, these reports suggest buyers want more flexibility and connected operations, while spending controls and unfinished requirements can complicate the move from interest to an order.
Let’s move from the equipment market into a machine shop. At HEI Precision, a few pallet positions are deliberately kept available for prototypes. A new part can come out for inspection or a program adjustment, and another job can go into the machine. Repeat work keeps moving while the new work gets sorted out.
Modern Machine Shop described the arrangement in October. HEI is a ten-person shop in Bellingham, Washington, built around repeat production. Its volumes differ from yours. What caught my attention is how it fits new jobs into an established schedule.
The repeat jobs have programs assigned to pallets and tools already in the machine. While one pallet is being machined, others can be loaded and scheduled. Redundant tooling supports repeated runs, including longer unattended stretches. So when a prototype comes out for checking, there’s already another prepared job for the machine to run.
The shop uses palletized horizontal and five-axis machines. Its president, Mark Holz, describes the prototype work as a way to develop new customers and markets alongside established production.
The scale of the work is worth keeping in view. The article puts annual usage for HEI’s production parts anywhere from two hundred to two hundred thousand pieces. That’s a very wide range, and some of it is far from short-run work. The useful comparison isn’t to copy the whole business model. It’s the deliberate space for first-time work inside a system otherwise prepared for repetition: the next job, its tools, and its program are already waiting while the prototype gets attention.
There’s another example in the article: HEI changed its whole process for shock absorber pistons. Previously, blanks were turned on a lathe, then loaded into three mills. Now, two robot-loaded mills make three pistons from each piece of rectangular bar. Their dual pallets let loading and flipping happen while the machine cuts on the other side.
HEI reports more output from those two mills than from the previous three, and up to twelve hours unattended after the material is loaded. It’s worth noticing what changed together: the starting stock, the sequence of operations, and the equipment. This wasn’t simply a robot added to the old process.
Changing piston size takes about twenty minutes, Holz says, including swapping jaws and repositioning the stock-locating pins. That’s within a piston family, not between any two drawings. It’s a useful success to understand. For your broader mix, though, I’d come back to the way HEI makes room for prototypes.
Holz says pallet changing has delivered his biggest automation return. That’s his assessment; the article doesn’t give a payback calculation. But it does give you something concrete to ask a supplier to demonstrate: a new part going in, coming out for checking, then going back while repeat work continues. I’d learn more from watching that than from watching one established part run again.
And now, something a long way from the shop floor. A pink rock found in the Sahara is helping researchers piece together what water was doing on Mars more than four billion years ago.
NASA reported on Teghaza 001 in late October. Discovered in Mali in 2022, it weighs a little under two pounds. Researchers found evidence that Martian water altered it around four-point-one billion years ago. The rock itself must have formed even earlier.
Like other Martian meteorites, it was blasted off Mars by an impact before eventually reaching Earth.
First, researchers had to establish where it came from. A team at the University of New Mexico examined its oxygen isotopes: forms of oxygen with different numbers of neutrons in their atoms. Their relative proportions can help identify a rock’s origin. Here, they matched the pattern in other Martian meteorites.
Then came the question of what history it had preserved. At first, it seemed to belong to a common class of Mars rocks. Yang Liu, who led the new study, almost passed on examining it. But unusual minerals and textures caught her attention. The team also found zircon crystals, which can preserve clues to a rock’s age and formation. There was more here than they’d first expected.
NASA places Teghaza among the three most ancient Martian meteorites found on Earth. Its interest isn’t just its age. Another ancient sample is composed almost entirely of one mineral; the meteorite called Black Beauty contains small volcanic rock fragments. Teghaza preserves a different mixture of igneous minerals. That mixture gives researchers another way to investigate how crust formed from cooling magma before water changed it. Two very old rocks can preserve quite different kinds of evidence.
To date that history, the researchers used rubidium and strontium. Radioactive decay changes their isotopic proportions over time, providing a clock. So the two isotope analyses answered different questions: oxygen helped establish where the meteorite came from; rubidium and strontium helped establish when events happened.
They examined individual mineral grains on a fragment smaller than a fingernail. Instead of dissolving the whole sample for one bulk measurement, they could study tiny areas and preserve more of the meteorite for future research.
The dating separates two events. First, magma cooled and formed the rock. Later, water altered it. The team dates that alteration to around four-point-one billion years ago, putting the rock’s formation earlier still.
There are two research publications behind NASA’s account. A June paper examined the meteorite’s water content. The October Science paper provides the initial characterization and dating discussed here. Together, they open questions about how water interacted with that ancient crust. They don’t establish a planet-wide climate from this one specimen, and they aren’t evidence of life. What’s new is the particular record preserved in this sample, and the possibility of studying it with methods that leave material for the next team.
Its composition also gave researchers something to compare with terrain observed from orbit. The mineral mixture resembles parts of Mars’s cratered southern highlands. They identified thirteen possible locations consistent with its mineralogy and chemistry, though they haven’t established exactly where it originated.
That’s where the laboratory work and spacecraft observations help each other. From orbit, scientists can compare broad stretches of terrain. In the lab, they can examine individual grains and date events recorded inside them. This little rock connects those two scales, giving researchers a sample of ancient crust they hadn’t had in this form before.
A pink rock found in a desert on Earth, still carrying the traces of water on another planet.
Sources
Packaging demand and the decisions before an order
pmmi.org
Packaging demand and the decisions before an order
pmmi.org
Packaging demand and the decisions before an order
pmmi.org
HEI Precision: repeat work, new parts, and a changed piston process
mmsonline.com
Teghaza 001: a piece of ancient Martian crust
nasa.gov
Simulated setup
BEKABLE: Tell me a little about yourself: your first name, age, and what you do for work.
David: I'm David, 52. I run a machine shop in Ohio. Thirty-five people. We machine steel and aluminum parts for companies that build industrial equipment.
BEKABLE: What would you like to keep up with, for work or outside it?
David: Material prices, what's happening with our customers, finding good machinists. And what other shops are doing with newer equipment. Outside work, space. Astronomy, missions, what we're finding out there. I used to read more of that than I do now.
BEKABLE: What pulls you into a space story?
David: A probe finally reaching somewhere, or a telescope showing us something we hadn't seen. I like understanding how they figured it out. I don't need to follow every launch or who's arguing with whom in the space business.
BEKABLE: What kind of equipment do your customers build?
David: Packaging machinery and material-handling equipment, mostly. We're making components to their drawings. Usually short runs, but plenty of repeat orders. A robot doing the same thing all day in a giant factory doesn't tell me much about our work.
BEKABLE: When it comes to your customers, what would you like to get a better sense of ahead of time?
David: Mostly the timing of their orders. Are their customers buying equipment, or putting projects off? It helps me think about the work we may have coming into the shop.
BEKABLE: What's coming up at the shop that you'd especially like to understand better?
David: We need to replace an older machining center. I want to get a clearer picture of what we should buy before we get too far into the sales pitches. A newer machine, maybe some automation. But it has to fit the work we actually have. I'm not looking for a daily list of machines for sale.
BEKABLE: What's driving the replacement: reliability, more work coming in, or jobs the current machine can't do?
David: Mainly reliability. It still runs, but keeping it running takes more attention than it used to. If we're spending the money, I'd like to know whether we can get more out of the replacement. We haven't won some huge contract that suddenly needs twice the capacity.
BEKABLE: Beyond reliability, what would you like the replacement to make better?
David: I'd like to get from one job to the next with less fuss. There's the setup, getting the first part right, checking it. Then the next job can need a different fixture. Some repeat jobs would be easier to leave running, but that's not the whole schedule.
BEKABLE: What about the people who would run the replacement?
David: We have experienced people. I don't want a purchase that assumes somebody can spend the whole week programming it and keeping everything fed. And finding someone who can handle a job from setup onward isn't easy. That matters more to me than just how many people we could hire.
BEKABLE: How far along is the decision?
David: We've started talking to suppliers. I'd like to replace it next year. No order signed yet.
BEKABLE: You mentioned material prices. Where do you buy your steel and aluminum, and how do price changes reach your quotes?
David: Mostly through metal service centers in the Midwest. We don't import it ourselves. For a new quote, we can use the current price. Once we've agreed on a job, it's harder to go back to the customer. I want to know what might be coming before I'm looking at a different number from the supplier.
BEKABLE: How would you like the briefing to sound?
- Casual and direct
- Friendly and relaxed
- Professional and approachable
- Formal and concise
David: Direct. Talk to me like someone who knows the shop, not like a sales rep. With the space stuff, explain what I need to understand. I'm interested, but I'm not a physicist.
BEKABLE: How much time would you want to spend listening? Six minutes, twelve, or another length?
David: Ten minutes works for me.
BEKABLE: I'll follow steel and aluminum supply, machining skills, and changes in how smaller shops work. For your customers' markets, I'll focus on what could affect the timing of orders for packaging and material-handling equipment, so you can put their requests in a wider context.
For the replacement, I'll look for accounts from shops doing work like yours, with enough detail to understand what changed and what they gained. That includes how they handle short runs and repeat jobs, and who does the work around the equipment.
I'll also watch what could change prices and lead times at your material suppliers, especially what would help before you commit to a quote.
And I'll keep astronomy and scientific missions in the selection: what they've found, how they found it, and what makes it interesting. Those stories can stand on their own.
Ten minutes, direct and concrete. What would you change?
David: That sounds right. Keep the broader manufacturing picture, too. I don't want the machine purchase to take over everything I hear.
BEKABLE: I'll give it extra attention while you're comparing options, while keeping the broader coverage. Under each briefing, Adjust my briefing lets you change a priority, add or remove a topic, or adjust the tone and length without starting over.
Priorities
- Raw materials and customers’ equipment markets
- Technical hiring and manufacturing developments
- Temporary focus: replacing an aging machine
- Astronomy and space exploration
Illustrative feedback
David: The piece on equipment orders was worth hearing. One thing I should add: a couple of our customers are doing more service work on equipment they've already sold. For the next few weeks, I'd like more on that side of the market, not just new equipment sales.
BEKABLE: Are you already quoting parts for that work, or is it something they're discussing?
David: We're quoting some replacement parts. I don't know yet how much of it will turn into orders.
BEKABLE: I'll give more attention to the equipment your customers help keep in service, and the replacement parts it needs. That's a market for your shop, separate from replacing your own machining center. I'll keep that purchase and your space interests in the selection, along with demand for new equipment.
One useful connection is parts availability for older machines. If an equipment maker has to support a model for longer, that can change which components it needs. I'll look for documented examples in your customers' markets. That could help explain a request for parts without treating it as evidence of a wider boom.
David: Yes. That's closer to the conversations we're having right now.
BEKABLE: I'll use that as a temporary priority. Once you know what those quotes are turning into, we can adjust it again.
Daniel’s complete briefing
Hi, Daniel! Let’s start with a detail in Microsoft’s supplier guide. A supplier can already be approved and still need another approval for the next piece of work. It’s worth following what happens when an assignment grows.
The guide is dated March. We’re looking at an existing buying process, covering suppliers that work with personal data, Microsoft confidential information, or AI systems for Microsoft. Services count, as well as software. These are Microsoft’s requirements, not a standard we can assume every large buyer follows.
Microsoft’s public program page adds a useful detail about timing: compliance runs on an annual cycle. For a new supplier, work can’t begin until the required compliance work is complete. Enrollment involves the supplier’s business sponsor, and some suppliers may be selected for an independent assessment against the data protection requirements. So there are several different things to establish: whether the work is in scope, which requirements apply, and what evidence is needed. The program doesn’t say every supplier provides the same assessment, and an existing commercial relationship doesn’t settle the scope of a new activity.
It starts with a description of the work. Suppliers build a data-processing profile: what information they handle, where they handle it, what role they play, and whether they use subcontractors or provide a cloud service. Those answers determine the requirements and assurances they need to satisfy. Approval to handle confidential information alone doesn’t include approval to process personal data.
The purchasing system checks two things: whether the required compliance work is complete, and whether the supplier is approved for the activity being purchased. Until both conditions are met, the engagement can’t move forward. So this profile has a practical consequence: it helps determine which work the supplier can take on.
Suppliers can change their profiles. If a change requires another approval, they get new tasks to complete before that approval arrives. Existing approvals stay in place meanwhile. They can keep doing the work already covered while qualifying for the additional activity.
Suppose a services firm starts by configuring a customer’s software, then proposes hosting part of the service itself. In Microsoft’s process, processing location and hosting activity help determine approvals. The expanded assignment can therefore require another qualification step, alongside a revised statement of work. Commercially, it’s one continuing relationship. For purchasing purposes, the activity has changed.
There’s a detail here for software companies using cloud infrastructure, too. The guide says most software-as-a-service suppliers need subcontractor approval when relevant data sits on a third-party platform. And where the cloud-services agreement requires an ISO 27001 certificate, Microsoft asks for coverage of the software service being supplied. A certificate for the data center isn’t the requested substitute. The evidence has to reach beyond the underlying infrastructure to the supplier’s service.
That’s why changing the wording of the agreement isn’t the whole job here. The supplier still needs to describe the activity, obtain the corresponding approval, and provide the evidence it requires. The broader statement of work and the purchasing approval have to catch up with the same change.
Let’s turn to a case where the wording of two agreements made all the difference. In September, New York’s First Department considered a three-point-six-million-dollar cap on construction delay damages. The cap held. The question was what else it covered. And one fact is essential: the general contractor was pursuing the owner’s losses, not its own.
The case is Gamma against Pavarini McGovern, involving curtainwall and facade work on a Times Square tower renovation. Pavarini was the construction manager and general contractor. Gamma was the subcontractor. The owner’s agreement with the general contractor and the separate facade subcontract gave the parties different rights. Keep those two agreements in mind; the distinction runs through the whole case.
The renovation was a forty-seven-story hotel, retail, and theater project. The contracts dated from August 2018. Gamma later sued the contractor for more than sixteen million dollars, alleging nonpayment and breach. Those primary claims had been dismissed and weren’t the subject of this appeal. What remained relevant here was the contractor’s counterclaim on behalf of the owner. That procedural history helps keep the direction of the claim straight: the appeal wasn’t deciding what Gamma should be paid for its work.
Under the owner’s agreement, missed milestones could trigger liquidated delay damages of ten thousand dollars a day, capped at three point six million. Those damages were the owner’s sole remedy for delay. The owner and general contractor also waived consequential damages against each other. But they hadn’t waived every other kind of damage.
The subcontract passed the owner’s liquidated-delay framework through to Gamma, including the cap. It also preserved other remedies for the general contractor, including consequential damages for the contractor’s own injuries. So the contractor had rights under the subcontract that the owner didn’t have under the main agreement.
The subcontract’s timely-completion provision was followed by another clause expressly preserving the contractor’s ability to collect other damages, including increased construction costs. That neighboring language mattered. The number appeared inside a particular damages framework, while the next provision preserved remedies outside it. Reading the number without its contractual surroundings was precisely the problem the appeal had to address.
Here’s how the owner’s claim reached Gamma. The owner had no direct contract with the subcontractor. Rather than sue the general contractor and have it pursue Gamma in turn, the owner arranged for the contractor to bring the owner’s claim under a pass-through agreement. The contractor’s liability to the owner for that claim was limited to whatever it recovered from Gamma.
That arrangement changed who could present the claim. It didn’t give the owner the contractor’s broader rights. Having waived consequential damages, the owner couldn’t recover them through the subcontract just because the contractor could have claimed them for its own injuries. There was no independent claim for the contractor’s own losses here.
But the owner also kept the rights it hadn’t surrendered. The lower court had read its waiver as giving up all damages except the liquidated amount. The First Department separated the provisions: the delay cap governed delay damages; the consequential-damages waiver excluded consequential damages. Neither eliminated every possible direct, non-delay loss.
The counterclaim alleged additional overhead and supervision, work costs charged by other contractors, storage, and labor expenditures. This was an appeal about dismissal, not an award of those costs. The court allowed the claim to proceed insofar as it sought recoverable damages outside the excluded categories. Consequential damages and delay damages above the cap remained dismissed.
What I find useful is the order of the reasoning. First, whose injury is being claimed? Then, what rights did that party retain? Finally, which limitation applies to which loss? Passing a claim through another party didn’t enlarge those rights or turn several distinct limitations into one overall ceiling.
You can keep that distinction in mind when a software implementation has service credits, a limitation in the main agreement, and remedies in a statement of work. That’s a comparison, not a software-contract ruling. Here, the appellate court rejected a single overall ceiling where the agreements had imposed narrower limits. The number stayed enforceable. Its reach was the issue.
Let’s leave the contracts there and take a walk through an older New York. Before the main Public Library building stood beside Bryant Park, its site held the Croton Reservoir. Four acres, twenty million gallons of water, and exterior walls fifty feet high. The water came from the Croton River in Westchester County.
And people went there for a walk. Bryant Park’s published history describes the reservoir walls as a popular promenade and viewing platform. Imagine an afternoon stroll along the top of a structure holding part of the city’s water supply. The same height that made it such a massive piece of infrastructure gave people a place to look out over New York.
The space to its west was called Reservoir Square. That’s where Bryant Park is now. It became Reservoir Park in 1870, then was renamed for William Cullen Bryant in 1884. The waterworks and the park were neighbors: the reservoir occupied the future library site, not the whole park.
And the space beside the reservoir had quite a life before it became a park. In 1853 and 1854, Reservoir Square hosted the Exhibition of the Industry of All Nations. Its centerpiece was New York’s Crystal Palace, inspired by the great exhibition building in London. Bryant Park’s history describes four thousand exhibitors showing industrial wares, consumer goods, and art. Alongside it stood the Latting Observatory, then New York’s tallest structure at three hundred and fifteen feet.
So there were two very different ways to look out over the city in this small area: the reservoir walls and the much taller observatory beside the exhibition. The fair closed as a financial failure in late 1854. The Crystal Palace burned down in 1858, and Reservoir Square later became an encampment for Union troops during the Civil War. By the time it became a park in 1870, the ground had already held industry, spectacle, and military use. The familiar library-and-park pairing came later.
By the end of the nineteenth century, the reservoir could no longer meet the growing city’s needs. The library replaced it and opened in 1911. But a piece of the old structure remains. Bryant Park’s history identifies a surviving segment in the lower level of the library’s South Court.
Construction of the library began in 1900, to designs by John Merven Carrère and Thomas Hastings. Its Upper Terrace connected the new building with the park. That detail helps place the change on the ground: the water-storage site became a place for books, but it also gained a new connection with the open space beside it. The two sites remained distinct while their relationship changed.
Before people came to that ground for books, they came for the view from the walls of a water reservoir.
And to finish, something to listen to afterward. There’s a record built around Linda May Han Oh on bass and Melissa Aldana on tenor saxophone. Just those two instruments.
Beneath Lifted Skies came out in August. An October Jazzwise review by Victoria Kingham offers a way in. The album includes standards, bebop pieces, improvisations, and solo performances, with no pianist or drummer in the lineup.
The album credits place the recording over two days in February at Wellspring Studios in Acton, Massachusetts, with Oh producing. The artist’s description frames the standards as material for discovery rather than nostalgia, alongside free improvisations and solo pieces. That’s the musicians’ presentation of the record, and it helps explain the range of the program without assuming every track works the same way.
The track list moves from Anthropology, just over three minutes, to pieces such as Duke Ellington’s Sound of Love, nearly five. There are fifteen tracks altogether, so the two I’m suggesting are an entry point, not a summary of the whole album. There’s enough variety in the program to explore beyond one kind of duet, while keeping that very small instrumental cast.
I’d start with their version of John Coltrane’s Twenty-Six Two. It runs two minutes and fifty-one seconds. Kingham points to a passage where bass and saxophone state the melody together. The bass is there in the foreground, carrying the tune alongside the tenor. That shared melody gives you something specific to listen for in their conversation.
Kingham hears both pressure and freedom in the reduced setting. Without piano chords or drum fills around them, each musician has more to carry and more room to move. That combination is the appeal in her description: the demands of playing with only one other person, and the possibilities that opens up.
Then try God Bless the Child, played on solo bass. Kingham singles it out as the standout performance. For three minutes and twenty-seven seconds, the bass carries the song alone.
Those two tracks together take a little over six minutes. Start with the short duet, then let the bass have the room.
Sources
Microsoft: supplier approval tied to the work
microsoft.com
Microsoft: supplier approval tied to the work
cdn-dynmedia-1.microsoft.com
Microsoft: supplier approval tied to the work
clarknuber.com
Gamma USA, Inc. v. Pavarini McGovern, LLC
nycourts.gov
Gamma USA, Inc. v. Pavarini McGovern, LLC
schlamstone.com
Gamma USA, Inc. v. Pavarini McGovern, LLC
nycomdiv.com
The reservoir beside what became Bryant Park
bryantpark.org
The reservoir beside what became Bryant Park
bryantpark.org
Linda May Han Oh and Melissa Aldana: Beneath Lifted Skies
lindamayhanoh.bandcamp.com
Linda May Han Oh and Melissa Aldana: Beneath Lifted Skies
jazzwise.com
Linda May Han Oh and Melissa Aldana: Beneath Lifted Skies
lindamayhanoh.bandcamp.com
Linda May Han Oh and Melissa Aldana: Beneath Lifted Skies
lindamayhanoh.bandcamp.com
Simulated setup
BEKABLE: Tell me a little about yourself: your first name, age, and what you do for work.
Daniel: I'm Daniel, 46. I'm a partner at a small law firm in New York. I work with service businesses and software companies, mostly on commercial contracts.
BEKABLE: What would you like to keep up with, for work or outside it?
Daniel: Decisions and legal developments that affect the agreements I negotiate. But also what's changing in my clients' businesses. Sometimes the business practice changes before anyone thinks to ask about the contract. Outside work, jazz and New York history.
BEKABLE: What do you enjoy discovering in jazz?
Daniel: Records I might have missed, new musicians, or a different way of hearing someone I already know. I like learning what the musicians are doing together. I'm less interested in lists of the ten essential albums everyone is supposed to own.
BEKABLE: And what draws you into a story about New York?
Daniel: Finding out what a place used to be and how people used it. A station, a waterfront, an ordinary building I might walk past. The city before it looked the way it does now. It doesn't have to be a famous landmark.
BEKABLE: Which agreements take up most of your week?
Daniel: Software subscriptions, service agreements, statements of work. Usually I'm on the provider's side. We draft their terms, then negotiate when a customer wants changes or sends over its own paper. For several clients, we're the outside lawyers they call regularly, not just for one transaction.
BEKABLE: Without naming clients, what kinds of software or services come up most often?
Daniel: Project planning and reporting software for service businesses is one example. On the services side, I work with firms that configure business software, move data over from older systems, and train the people who'll use it. That's not everyone, but it gives you a picture of the work.
BEKABLE: When you say you want to follow changes in their businesses, what would be useful to understand earlier?
Daniel: What customers are starting to expect from them, and what they're promising in return. Different ways of charging, handling customer information, relying on another company's technology. I want some context before I see a new request in a redline.
BEKABLE: Is there anything coming up that deserves extra attention for a while?
Daniel: Two software clients are going after larger customers. I'm helping them prepare for those negotiations. I'd like to understand what those buyers are asking suppliers to demonstrate, particularly around data and service commitments. I know the clauses. What I don't always see is the buying process behind them.
BEKABLE: What do you know about those buyers so far?
Daniel: Mostly larger U.S. businesses. I wouldn't narrow it to a single industry yet. The conversations are early, and I don't want to build the whole briefing around a deal that might not happen.
BEKABLE: Which jurisdictions come up in your work?
Daniel: Most of the contracts I handle use New York law. Some use Delaware. The clients mainly sell in the U.S., though an overseas customer comes up occasionally. I don't need every development from every jurisdiction just because it's about software.
BEKABLE: What usually makes a legal or business update worth your time?
Daniel: It gets to what actually changed. A case can be useful because of the facts and the court's reasoning, even if it's not a rule for every client. On the business side, give me something a company is actually doing. I can make more of that than another prediction about how everything will be transformed.
BEKABLE: How would you like the briefing to sound?
- Casual and direct
- Friendly and relaxed
- Professional and approachable
- Formal and concise
Daniel: Professional and approachable. Direct, but not like someone reading a case digest aloud. You can use the legal terms. With music, explain enough that I can hear what you're getting at when I listen to the record later.
BEKABLE: How much time would you want to spend listening? Six minutes, twelve, or another length?
Daniel: Twelve minutes. Enough to get into something, not just hear a list of headlines.
BEKABLE: I'll follow developments relevant to the software and service agreements you negotiate, along with changes in how your clients sell, deliver their services, and depend on other providers. That gives us a reason to look beyond legal news when a business practice starts changing the agreements around it.
For now, I'll give extra attention to what larger business customers expect from software suppliers, especially around data and service commitments. I'll look for documented buying requirements and examples you can put beside what you're hearing in negotiations, while keeping the rest of your practice in view.
You'll also get jazz worth spending time with, and stories about how New York's places have been used and changed. Those can stand on their own. The recordings and places will be there to explore after listening.
Twelve minutes, direct and precise, with room to explain. What would you change?
Daniel: That sounds right. Don't let every music story turn into a story about New York, though. I'm interested in jazz wherever it's being made.
BEKABLE: I'll keep jazz open to what's happening elsewhere, and New York stories won't always revolve around music. When there's a connection worth exploring, there's room for that too. You're ready for a first briefing. Under each one, Adjust my briefing lets you change a subject, priority, tone, or length without going through this conversation again.
Priorities
- Commercial contracts and relevant legal developments
- Business practices of service companies and software publishers
- Jazz, as an interest in its own right
- New York history, as an interest in its own right
Illustrative feedback
Daniel: One thing has come up since we talked. A software client is considering charging by usage instead of just by seat. For the next few weeks, I'd like more on how companies are making that work, especially what customers can actually check on the bill.
BEKABLE: Have they chosen a model, or are they still comparing options?
Daniel: Still comparing. Their current contracts are annual, per seat. They haven't announced a change. I'm interested in how others define what gets counted, deal with disputed usage, and give customers some visibility before an invoice arrives.
BEKABLE: I'll give usage-based pricing and billing practices more attention for now, using published terms and documented examples. I'll keep the broader contract coverage, larger-customer negotiations, jazz, and New York history in the mix.
There's a related question worth watching: whether the software company's own providers charge for the same activity it's considering billing to customers. If the two measures differ, that could matter to the model they're comparing. I'll look for examples where those measures are explained, without assuming how your client's service is built.
Daniel: Yes. That would help me understand the options before we're negotiating the wording.
BEKABLE: I'll treat it as a temporary priority while they're comparing models. Once they've chosen a direction, you can tell me what changed and we'll adjust from there.