Meridian Espresso

Company

• Business name: Meridian Espresso
• Legal name: unknown
• Business category: unknown (name suggests a cafe/espresso bar, but this is inferred from the name only, not confirmed)
• Website: unknown
• Instagram: unknown
• Number of locations: unknown
• Account owner: unknown (internal account owner not specified)

Locations

Location 1

• Location name: unknown
• Address: 72 W 38th St, New York, NY 10018
• Opening date: unknown
• Shipping address: unknown
• Status: unknown

Contacts

Contact 1

• Name: Danny Reyes
• Role: Owner
• Email: danny@meridianespresso.com
• Phone: unknown
• Preferred channel: in-person (email introduction sent, but cold email is assessed as unlikely to get a response; Danny's on-site schedule is described as random/unpredictable)
• Decision role: owner (assumed decision-maker based on "owner" title; not otherwise confirmed)

Commercial Information

• Current matcha supplier: unknown
• Estimated monthly usage: unknown
• Payment terms: unknown
• DUNS number: unknown
• Notes: Cafe sells cookies noted as good by our team; a pairing idea (nacho-flavored matcha latte + cafe's cookies) has been proposed internally but not yet pitched to the customer.

Data Quality

• Last verified: 2026-08-04
• Verified by: context drop note (_inbox/2026_08_04_text_note-12.md)
• Open profile questions: confirm business category, website, Instagram, location/address, and number of locations; confirm Danny's decision-making authority; confirm whether the 2026-07-16 introduction email has received any response; establish a reliable way to reach Danny given his unpredictable on-site schedule. Address sourced via web search on 2026-08-04, not yet confirmed by direct customer contact.

Current Situation

Meridian Espresso is a cold-outreach prospect where owner Danny's email was obtained during a 2026-07-16 visit and an introduction email was sent the same day. A revisit on 2026-07-22 found Danny not on site; staff described his schedule as random/unpredictable, making it hard to plan a return visit. On 2026-07-23, the team tried the cafe's cookies (found them good) and formed a product-pairing idea — a nacho-flavored matcha latte alongside the cafe's own cookies — intended for a follow-up email once Danny is reached. Cold email is assessed internally as unlikely to get a response without a warm introduction, so the near-term plan is repeated in-person visits to catch Danny directly.

Key People

• Danny — Owner — assumed decision-maker (per "owner" title, not otherwise confirmed); on-site schedule is random/unpredictable, not yet met in person by our team.

Customer Needs

• Primary use case: unknown
• Expected volume: unknown
• Flavor preference: unknown
• Color preference: unknown
• Target price: unknown
• Lead-time requirement: unknown
• Packaging preference: unknown

Commercial Assessment

• Current stage: contact — introduction email sent 2026-07-16; owner not yet reached in person (as of 2026-07-22 revisit)
• Interest level: unknown — no response from Danny recorded yet, by email or in person
• Urgency: unknown
• Primary blocker: Danny's unpredictable on-site schedule makes in-person contact hard to time; cold email response is considered unlikely without a warm introduction
• Buying readiness: unknown
• Opportunity potential: unknown — no usage, volume, or business details confirmed yet
• Main risk: repeated visits with no owner contact could stall the lead indefinitely if Danny's schedule stays unpredictable and email goes unanswered

Product Fit

• Preferred SKU: unknown — no discovery conversation has occurred
• Recommended SKU: unknown — insufficient information to recommend
• Reason for recommendation: not applicable yet; internal idea to pitch a nacho-flavored matcha latte paired with the cafe's cookies has not yet been presented to the customer
• Alternatives: not applicable yet

Open Questions

• Has Danny responded to the 2026-07-16 introduction email?
• What are Meridian Espresso's business category, location, website, and Instagram?
• What is Danny's actual decision-making authority (sole owner vs. shared)?
• Is there a more reliable way to reach Danny than repeated unannounced visits?

Current Recommendation

Continue repeat in-person visits to catch Danny given his unpredictable schedule, since cold email alone is considered unlikely to get a response. When following up by email or in person, reference trying the cafe's cookies and pitch the nacho-flavored matcha latte pairing idea as a way to re-engage.

Evidence Used

• Timeline event: timeline/2026-07-23-cookie-tasting-and-pairing-idea.md

Active Actions

action-001

• Action: Keep revisiting Meridian Espresso in person to catch owner Danny on site
• Type: outreach
• Reason: Danny's on-site schedule is random/unpredictable (per staff, as of the 2026-07-22 revisit); cold email response is considered unlikely without a warm introduction, so in-person contact is the primary path
• Trigger: Revisit on 2026-07-22 found Danny not on site
• Owner: unknown
• Priority: medium
• Status: completed
• Due date: not specified (try again on a different day/time)
• Approval required: no
• Agent permission: recommend_only
• Required inputs: none
• Completion condition: Danny is met in person, or a tasting is scheduled
• Created from: timeline/2026-07-23-cookie-tasting-and-pairing-idea.md
• Result: Sent via Executables on 2026-08-05: "Following Up on Our Recent Visit"

action-002

• Action: Send a follow-up email to Danny mentioning the cafe's cookies (tried and found good) and pitching a pairing with a nacho-flavored matcha latte
• Type: follow_up
• Reason: The pairing idea came from tasting the cookies in person on 2026-07-23; referencing it may help re-engage Danny once reached, since the original introduction email has gone unanswered
• Trigger: Cookies tasted 2026-07-23; introduction email sent 2026-07-16 remains unanswered
• Owner: unknown
• Priority: low
• Status: proposed
• Due date: not specified
• Approval required: yes
• Agent permission: draft_only
• Required inputs: confirmation that Danny has been reached or is otherwise reachable by email
• Completion condition: Follow-up email sent to danny@meridianespresso.com
• Created from: timeline/2026-07-23-cookie-tasting-and-pairing-idea.md
• Result:

Waiting on Customer

waiting-001

• Item needed: Response from Danny, by email or in person
• Requested on: 2026-07-16 (introduction email); revisit attempted 2026-07-22
• Follow-up date: not specified (try again on a different day/time)
• Related action: action-001

Scheduled Follow-ups

• None scheduled yet.

Completed Actions

• None yet.

Summary

Context drop (typed note) covering the full Meridian Espresso pipeline history to date: an initial visit on 2026-07-16 where an email address was obtained and an introduction email sent, a revisit on 2026-07-22 where owner Danny was not on site and staff reported his schedule as random/unpredictable, and on 2026-07-23 trying the cafe's cookies (found to be good) and forming a product-pairing idea. Cold email outreach is assessed as unlikely to succeed without a warm introduction, so the plan going forward is repeated in-person visits to catch Danny directly, plus a follow-up email that references the cookies and pitches pairing them with a nacho-flavored matcha latte.

Extracted Facts

• Fact: In-person visit and email obtained

  • Value: Visited Meridian Espresso on 2026-07-16; obtained owner Danny's email (danny@meridianespresso.com); sent an introduction email the same day
  • Scope: opportunity
  • Status: confirmed
  • Source: _inbox/2026_08_04_text_note-12.md (note cites Raw/2026_07_22_voice_note_8.md and Raw/2026_07_23_voice_note_3.md, neither independently available in this CRM)

• Fact: Revisit — owner not on site, schedule unpredictable

  • Value: Revisited 2026-07-22; owner Danny was not on site; staff reported his schedule as random/unpredictable, making in-person contact harder to time
  • Scope: contact
  • Status: confirmed
  • Source: _inbox/2026_08_04_text_note-12.md

• Fact: Cookies tasted, product-pairing idea formed

  • Value: Tried the cafe's cookies on 2026-07-23; found them good; formed idea to pitch pairing them with a nacho-flavored matcha latte
  • Scope: opportunity
  • Status: confirmed
  • Source: _inbox/2026_08_04_text_note-12.md

• Fact: Cold email strategy assessed as ineffective

  • Value: Cold email outreach is assessed as unlikely to get a response; a warm introduction or in-person contact is seen as required instead
  • Scope: opportunity
  • Status: inferred (stated as an assessment/opinion in the note, not an observed outcome such as a non-response or rejection)
  • Source: _inbox/2026_08_04_text_note-12.md

Customer Commitments

• None identified.

Our Commitments

• Introduction email sent to danny@meridianespresso.com on 2026-07-16.

Questions Raised

• None identified.

Products Discussed

• SKU: unknown — no specific SKU named
  • Use case: Proposed pairing of a nacho-flavored matcha latte with the cafe's own cookies, as a combination expected to sell well
  • Feedback: Not yet pitched to the customer; idea originated from our own tasting of the cafe's cookies, not from customer feedback

Original Evidence

• Source channel: note (typed directly into the chat feed)
• Source reference: _inbox/2026_08_04_text_note-12.md (Job: 6f240cc2cb4a); note also cites Raw/2026_07_22_voice_note_8.md and Raw/2026_07_23_voice_note_3.md as its own sources, not independently available here
• Relevant excerpt or transcript timestamp: "## Activity Log\n- 2026-07-16: Visited cafe, obtained email address\n- 2026-07-16: Sent email introduction\n- 2026-07-22: Revisited cafe in person, owner Danny not on site; schedule reported as random/unpredictable\n- 2026-07-23: Tried the cookies from the cafe, they're good\n\n## Next Steps\n- Action: Keep revisiting to catch Danny in person\n- Reason: Email response unlikely (warm introduction needed); Danny's schedule is random, so timing an in-person meeting requires repeated attempts\n- Action: In the follow-up email to Danny, mention trying the cookies (they're good) and pitch pairing them with a nacho-flavored matcha latte as a combination expected to sell well"