Danny and Ryan worked through a pre-meeting document and proposal framing ahead of a conversation with the client (Sal and Ryan Beck at Allegiance) about the future scope of MyBill. The session covered both near-term contract positioning and longer-term product directions, with the two of them editing a shared document in real time, reviewing screen-shared content, and debating what to include, cut, or reframe.
On the contract and pricing side, the core tension was whether to propose a flat-fee software subscription, a retainer, or some hybrid. Ryan raised a concern that coupling a large upfront license fee with an ongoing retainer could read as double-dipping to the client. Danny acknowledged this but leaned toward framing the ongoing engagement as covering expansions and consulting beyond the core product, keeping the software subscription and professional services conceptually separate. They did not settle on a specific rate or structure, but agreed the conversation should stay at a higher level and avoid surfacing past problems or scope that was never promised.
On the product itself, Ryan walked through several recent additions to MyBill: preflight validation blocks that flag anomalous pricing codes, promo codes, and unfamiliar bundles before billing is finalized; an event log and activity tracking that lets Ryan monitor when Ryan Beck logs in and what actions he takes; and dedicated pages for pricing codes and plan types. Ryan also noted the quoting tool already built into MyBill has never been used by Ryan Beck. These capabilities were flagged as worth highlighting clearly in the proposal, particularly the validation and pricing-engine framing, with the acknowledgment that the existing description of what MyBill does understates its core value as a unified pricing engine.
Potential expansion areas discussed included a stripped-down, mobile-friendly sales quoting view (judged as very low effort and potentially includable in the base scope), a read-only MCP or Copilot-style query layer for quick lookups, a basic inventory tab, and documentation with embedded screen-recording walkthroughs. More speculative ideas—predictive reorder nudges, Clay CRM enrichment, deep telematics analytics via Motive or Geotab, and an AI-driven ordering flow—were either deferred or set aside as too hard to deliver reliably. Ryan flagged that AI adoption buy-in from non-leadership staff would be difficult regardless of what is technically feasible. The framing of expansion items in the document was landed on as "potential areas of expansion" rather than "optional add-ons."
Ryan also resolved a question from earlier: the Proceed test database has not been sunsetted, which opens up safer testing as the team moves toward integrating Allegiance. On the CI side, Ryan shared that he moved automated browser tests to a local Docker instance after hitting GitHub's free-tier CI cost ceiling. The meeting ended with Danny planning to send the proposal document, possibly that evening or the next day.
Yo, hang on. I gotta throw my headphones, and you might have some echo for a second. Okay. How we doing, man? How's the rest of your day?
Oh, good. Tired though, But yeah, not bad. Yeah. I did some more research into our proceed integration. I had thought that they had sunsetted our test database, but they haven't. So that might open up more potential flexibility with I guess, trying new things within proceed within, you know, obviously limited scope. But like, especially as we move towards adding in allegiance, I think that'll make things really a lot easier. I mean, testing in prod is not something I want to do, so.
Yeah. And I think dad wasn't. Doesn't quite understand, like, I think he was just like, yeah, we got the arrangement figured out. And then Ryan. And Ryan's like, yeah, well, let's just. Just, like, populate direct, you know? Like, let's. It's all right. I think it's both. I mean, I think it's just both will happen. I think it's like a slow.
Yeah, I mean, I think. I don't know. I. Well, it's kind of a business decision of whether you have it be built as a parts ticket from Ascendance Leasing.
I just see them. If those two are going to drive, like, eventually coalescing on, like, there's just a direct. Whatever. So there's not even. I don't know, maybe they start, like, measuring time. Like, actually on some of this. Like, the. The accounting team. Are they under threat? Maybe. Anyway. Okay, so. Okay, so let's. Share my screen in a second here. I'll reorganize this later. Okay, so. Okay, so the big things that they flagged that we didn't already include in the like 33,000 and sorry, 36,000, yada yada, that I saw from Saul
16.
was like the. Okay, like, what's your rate? Like, you know, how do you plan on doing this? And we said, oh, flat fee. And again, I still think it's like we're consultants, like, building them software at least there's like a twinge of that. Maybe that cleared up when I was like, well, it's the subscription fee for the software. I imagine they could just throw in. Oh, yeah, we own this now. Right. And we'd want to be ready for that. But outside of that, anything else from your research or just thinking since the meeting that you'd want to like, incorporate into the conversation.
I think the idea behind how do we make it so not only Ryan Beck knows how to use this, and if Ryan Beck's on vacation, this can still be a useful tool. And upskilling salespeople, for example. I think those are really. Those are things that we can talk about is like extensions upon the existing contract, which would just cover the software as it is up to 4,000 devices.
Okay, One second. Pulling the picture from the transcript, because I was looking at. Yeah. And so that I'm just going to drop this in. And this is the one. I'm not sure the Azure, specifically, like, I,
that'd be too bad.
I mean, I, I did. I was looking into it based on our current stack. Doesn't look that ridiculous. I just have never used any of those tools, so.
I don't think it'd be bad. It.
I mean, that's the, that's the bare bones. The things from the transcript was this for these general ideas from that in the, in the debrief, the full quoting obviously being very interesting. I think you're probably right that like the teams piece might. Because we don't even know if people are actually using teams. I know Saul uses teams and so solid. Probably all about the teams, whatever. Which maybe is like, we don't care if the sales guys use it. They need it. They have to. They have to like. But do you see just like the mobile friendly plus stripped down view only show quote flow for sales guys?
That would take two seconds to make. And yeah, I mean there's already a lot of lot in place in terms of like scoping views to specific user classes. So a sales user class would just be an addition to one of a list and then you just expose quotes. Very easy to do. That wouldn't even be like, like. I honestly think we could say we'll include this with that because it's literally a two second edition. But then the, the piece could be, you know, we could help. I don't know if there's any consulting side of like how we could help with that or if it all just would just be Ryan Beck upscaling.
Yeah, I mean there's like, there's some interesting things like a clay integration, for example, which is just a simple API API key layer to allow for like enriching beyond the quote other elements to try to like make the quote more personalized. For example, like that, that could be something that's just like a bolt on. I don't know if that's interesting. I just, I know that actually I don't know what their CRM is, but I think they have one now. Would it be Salesforce?
I I do hesitate just on the again integrating with another service of theirs just for like that's when you start to get the stalling back and forth added layer of complexity managing within their environment, etc. Etc. That annoying
you're right. And that's why I think things like
just which again are lower lift but like predictive ordering forecasting like nudges to have one click copies of email bodies of like hey, to XYZ client that I'm looking at or is on this dashboard like you ordered blank at this period. Like, you know what I mean? Like studying the patterns of hardware ingestion and sale. But then some of the inward patterns of like I don't think they're doing much of the buy hardware sit on it and sell it out. But for if that's, if any of that is still present, like basic inventory just it's just like another tab which is just a layer of an existing database. Like I don't know, I think like those little things like are small wins that do make this like the operational surface for the entire workflow. And that's
We could there are API endpoints for basically everything in my admin. Like, we could become my admin. We could, we could reverse engineer all of the ordering features that exist on my admin right now and include them in my bill. And then, I mean, try to get to a point where Ryan Beck doesn't even use my admin. And then this is the engine for everything that's, you know, I don't think that that's something that would be concluded in the scope of what we're saying we'll offer right now. But I think that that's another thing where it's like I think Sal was asking, maybe it was Ryan, but one of them was asking like, so you still have to use my admin, right? Or whatever. So, like,
well, what if you didn't and what if you owned all that? And yeah, I mean, we could abstract a lot of that away.