Estimating from blueprints

“Gave Athena the spreadsheet, explained which column I was trying to figure out, and then ten secs it told me... exactly how the calculation was based on the other data.”

“He wrote the entire stuff. By itself. And I was there, and I was thinking, alright. If I had to write all this stuff, I mean, I would've spent days, days, days.”

“I send that to the programmer and he said, alright. I read your file. I copied the section of the code because he has the right interface, and it works. Wow. Just like magic.”

“One workspace. All different, let's say, avatars of their output data. Right? Suddenly, it's dashboard. Excel is here. PowerPoint is when it's all together. It's very impressive.”

“Use the Athena platform probably closer to the concept and how it was designed, like, with the spaces architecture where you've got a set of primitives and capabilities, and you bring together the right set of capabilities to solve a task.”

“Digital worker, it gets spun up, it gets given access to the toolkits that it needs. It gets given access to the data that it needs. Just exists for the period it needs to exist to perform the task. And then it gets torn back down again afterwards.”

“I like that direction, that concept of the agent is the agent. It becomes an entity in its own right with its own ownership and its own missioning, and you get rid of the gray area and the blurry lines.”

“A lot of people are telling us that, oh, I sold in this package because of this info... I secured this distribution because of the selling assistance help.”

“I finally got a chance to play around with the computer asset and build out the chatbot you mentioned. It was really impressive.”

“So we use the SDK, and we write that in Python, and it calls Athena majority by API. The results appear in the interface itself.”