Prismatic Reviews & Product Details

The practical part was being able to focus on the actual data flows rather than treating the project as a generic integration exercise. That made it easier to think about how the information would be used by the accounting and finance team after it moved between systems. Review collected by and hosted on G2.com.

We had some back-and-forth early in the project because a few requirements weren't completely clear at first. We had to revisit some of the details before everything was defined the way we wanted it. Review collected by and hosted on G2.com.

The useful part for us is being able to build workflows around the way our business actually operates. We could account for the different information moving through our home-preparation projects instead of treating the integration as a one-size-fits-all setup. Review collected by and hosted on G2.com.

There was some back-and-forth at the beginning while we clarified requirements and worked through a few edge cases. It wasn't a major issue, but we did have to follow up on some details before everything matched our process. Review collected by and hosted on G2.com.

The pre-built connectors are the biggest advantage for us. We didn't have to start by building the Google Ads connection ourselves, so we could spend more time defining the workflow and less time dealing with the underlying API work. Review collected by and hosted on G2.com.

I had to follow up a few times to get updates or clarification during the project. It wasn't a major problem, but I would have preferred having some of that information pushed to me without needing to ask. Review collected by and hosted on G2.com.

The biggest benefit is having the integration layer in one place instead of having separate pieces of integration logic scattered across different applications. For a company working heavily with APIs and enterprise GIS, that makes the overall architecture easier to work with. Review collected by and hosted on G2.com.

We had some back-and-forth at the beginning while we clarified requirements and worked through how particular data should flow between systems. It wasn't a major problem, but getting those details nailed down earlier would have made the initial phase more straightforward. Review collected by and hosted on G2.com.

The useful part was having the integration work structured around APIs and existing cloud services rather than forcing us to create a completely separate integration architecture. That is particularly relevant when you're dealing with blockchain infrastructure alongside conventional cloud applications. Review collected by and hosted on G2.com.

Some requirements had to be clarified more than once during the project, so there were a few points where we needed additional follow-up. It didn't prevent completion, but the initial requirements could have been tighter. Review collected by and hosted on G2.com.

The biggest benefit is being able to build the synchronization around the way our accounting workflows actually operate. Having the integration logic handle data movement gives our team less manual coordination to deal with. Review collected by and hosted on G2.com.

There was some extra back-and-forth at the beginning while we worked through the requirements and clarified exactly how the data needed to flow. It wasn't a major issue, but we did need a few additional follow-ups before everything was clearly defined. Review collected by and hosted on G2.com.

The flexibility around APIs, data mapping, and integrations is the biggest benefit for us. It gives our team a more structured way to handle the connection between our platform and tax software. Review collected by and hosted on G2.com.

The integration work still requires some iteration, especially when you're dealing with the details of how tax data maps between systems. That's more of an implementation consideration than a major issue, but it does mean some areas need to be worked through carefully. Review collected by and hosted on G2.com.

The useful part is being able to approach integrations through a common platform rather than treating every API connection as a completely separate development project. It gives our team a more consistent way to build and manage those connections. Review collected by and hosted on G2.com.

Some requirements needed to be clarified after the initial work started, so there were a few extra follow-ups before we had everything configured the way we wanted. It wasn't a major issue, but it did add some back-and-forth. Review collected by and hosted on G2.com.

The biggest benefit for us was having the integration infrastructure organized around the actual workflow rather than treating the API connection as a one-off coding task. It made the Plaid work easier to think about as part of a broader integration strategy. Review collected by and hosted on G2.com.

We had some requirement clarification to work through at the beginning. A few assumptions about the workflow weren't quite right, so we needed additional follow-ups before everything was lined up. Review collected by and hosted on G2.com.

The biggest benefit for us was having existing connectors available instead of starting every integration from zero. That made it easier to look at the workflow as a whole and decide where we actually needed custom work. Review collected by and hosted on G2.com.

There were a few points where we had to go back with additional questions before the data flow was clear. It wasn't a major problem, but some of those details could have been clearer earlier in the project. Review collected by and hosted on G2.com.