The initial setup is very simple and straightforward. 

Their documentation is pretty good. If you go through that, you'll be able to easily set it up properly.

The first part of the deployment is a bit tricky. When you apply and fill in the signing form, they review it to see whether or not you are registered - which is a good thing since, nowadays, people are spamming a lot. 

If a spammer gets access to a platform like this, they will be able to send multiple emails, and it could harm people. That's why they do due diligence, and they would like to know your history, how you want to send the email to people and whether the people you are sending to signed up with you or not. If they find that you are a legit sender, then only they will approve your account. That's the part that takes some time. Once it is approved, then it hardly takes a single day or two to finish the rest of the setup.

The implementation process varies in difficulty. If you only want to try to connect it with something very simple, it's easy. It's based on the applications that you have on your side and the complexity of the message that you want to send.

You need to develop a tree of communication, and also that will be a factor. If the tree is complex, the setup will be complex.

For example, if you want to only send an email each time a client buys something and send a thank-you message after the purchase, and you don't need to personalize anything, that will be very quick. If you are on the other side and based on a lot of complex rules, maybe for a financial investor on a stock change and you need to send a lot of warnings on the information of operation, that could be tougher.

That said, in general, it's very easy to integrate, and it's something that, even if you didn't work with it in the past, you could learn easily.

Since it's software as a service, we only need to check that it's working. When the endpoint sends an error message, we need to check on that. Other than that, it doesn't require maintenance.

The initial setup is easy. Actually, The deployment takes 10 minutes to one hour. It depends on the domain and the type of the domain. Most of the time, when you add a domain on SendGrid, it seems like it's real-time. I have no problem with it.

The implementation process is extremely straightforward. 

We do not need any staff for deployment and maintenance tasks. 

The solution is very straightforward and simple. It's easy compared to other products I've used. 

I'd rate the ease of setup nine out of ten.

The deployment is just a matter of a few clicks. I just used it to get the API key and use that in my code. Other than that, for building templates, creating funnels, and stuff like that, I'm not handling that. I have not used that portion. 

It was straightforward. It was not very difficult. The SendGrid documentation is good enough, and its setup is fine.

There are two different sides to it. The marketing and email side is straightforward. It is there by default. You just upload the customer contacts and start writing things. On the automation side, integration needs to be done. The documentation is straightforward.

In terms of duration, the marketing bit is off the bat, so it doesn't matter. For the API bit, it was not really a matter of any integrations to be done from the SendGrid side. It was just that the solution from our side took some time, but integration was never a problem. It was straightforward. Overall, I would rate its setup a four out of five.

The initial setup for SendGrid is easy, and the tool took one month to deploy.

The solution's initial setup is straightforward. It takes only a few minutes. Once you upload the sample code to your back end, you can begin using the solution.

No setup needed. You don't have to install anything, just use a very well documented API. Also, with .NET framework, there is an official Nuget package that makes the use of SendGrid even easier.

But on the other hand, it could be very complex if you decide to move all the emails that your applications generate to SendGrid. You will have to make a lot of code changes.

We decided to start by using SendGrid only on new notifications. And if we had to alter an old email template, we take advantage of that and make it through SendGrid also.

I think that also the GUI for creating the templates is very simple. I only have used it a couple of times so not really a review on that function here.

It was easy for me as I'm a software developer and Unix system administrator.